Bechu kumar pandit

Okay. Uh, my name is Basikumar Pandit, and I have a 5.7 years experience in a, uh, back end side. Uh, I'm working on a, uh, as a senior Node. Js developer in my current company. So my technology is mainly, uh, Node. Js Microservices AWS. For the AWS part, we can we can select EC 2, SQS, SNS, and s 3 bucket. And for the Docker, uh, for the Docker and, uh, Microservices and Redis, Kafka, etcetera, uh, like that, uh, I have experience in that, uh, current company. So current currently, I'm, uh, handling, uh, one project. There is a, uh, like, a logistic project name and another one is a credit allocation. It means, like, suppose for we are talking about, like, a, uh, credit allocations. That means, uh, that means, like, uh, we have a multiple, uh, like, product coming from the different different ecommerce platforms like Flipkart, Amazon Flipkart. You can say, like, Myntra, any any other server like Amazon. So there is a we can maintaining. According to that product, we can maintaining all query services according to weight wise. So there is a decided, uh, there, uh, we have, uh, some prices according to, um, weight wise. So according to, um, suppose, uh, there's a different query service we can see is, uh, firstly, blue dot, uh, expressv's, and Nimbus post, uh, then, uh, d t d c. This type of query service we have. So we can we can, uh, we can, uh, create that project from the scratch method. So I have a, um, so in that particular, uh, applications, so we can we use Node JS, Tapascrip, uh, MongoDB, and, uh, SQS for the, uh, we can select a message broker. We can using, like, a queue. Uh, and Microsoft, we can already tell, uh, told, uh, there is a in Docker, uh, Docker for the deployment part. We can we can tell, uh, these things. So this type of technology I have worked, and, uh, according to current company, so I'm working on a logistic part. It means, like, it's a b to b business, uh, product. So logistic part, if you're handling, like, trip. Suppose we have a bulk in bulk, uh, product, so we can send to the, uh, one to another places according to, like, vendor wise. So, uh, we can generate a trip. So trip will decide it from the sales order and invoices ID. So because of there is a one sales order, but there is a multiple invoices. So according to it twice. So we can decide these things according to trip. So we can generate in trip, then we can allocate that path, uh, where they will go, and we can generate reports. Uh, we can generate in this type of problems in that, uh, application. We can manually all those things according to this thing according to, uh, my applications. So approx these things, uh, I have worked on worked on that technology. And technology is the same, uh, Node. Js microservices and, uh, MongoDB. And Redis, we can, uh, Redis, we implemented. And Kafka for the micro service communication for, uh, that purpose. So I have here these things. So that's fine for my end. So okay. Fine. So I have a knowledge in React JS also. So not a deep knowledge, but, uh, I have a React JS knowledge also. So I can do React JS as a functionality part, not designing part. So I know it, uh, how to implement React, Redux, and the, uh, Redux toolkit and hooks. That con concept. And I know oops concept, uh, object oriented program.

So, uh, yeah. Uh, so, basically, too low, uh, I used in, uh, message for the messaging, uh, like a phone number, and, uh, we can select a email. Uh, for that purpose, I have used, uh, Tulo. So, uh, basically, uh, Tulo, uh, only that purpose I have used because of, uh, and, uh, because of, uh, we can we can verify OTP and, like, uh, different things, uh, in a, uh, in a Node. Yes. So, uh, we implemented, uh, in a toolo API integrations. So that that's it. Nothing more than that. I think, uh, too low. Uh, only, uh, only in notification for the notification part, and I have implemented these things. That's it. Uh, I think nothing more than that. So, uh, if I can I can say, like, how to implement this as according to coding level now? So firstly, we can go, like, a tool account. We can creating tool account then, uh, after creating API, uh, after creating a sign up, then, uh, there is a one for the develop for the developer part. So we can say, like, a big credential. So we can implement maintain, uh, a big, uh, like, epic credential wise. So we can we can, uh, we can, uh, install package, uh, to or Tolo. Uh, we can implement it like a Tolo. So, uh, we know our NPL installed Tolo. Then after that, uh, uh, all credential account IP like likes, uh, like that. Yeah. Auth auth tokens. These two things, so we need that then. Uh, we know, uh, how to, like, uh, it's a message. Uh, we can say, like, there is a one type of, uh, like, uh, some line of code. We can say, like, client dot message. Suppose we can we can declare, like, a client call to Tulo and account ID, like, uh, account ID and auth tokens. So we know all these things according to client dot message. We can implement it like that one, a client dot message. So whatever message we can throw in a body part or, um, body part, we can we can, uh, just put it and directly send to the message. And OTP if we know OTP, um, send all for the mobile verification, then we can implement it, these things. After that, uh, like, uh, additional, we can, uh, taking, like, a WhatsApp also, what, uh, what, uh, in a WhatsApp integrations. Also, we can do do these things, phone number, email, and WhatsApp. Those things, uh, we can implement it, uh, on that uh, particular, uh, part. So that's it. Um, nothing more than in a tool API document because we know all documentation API levels. So we can implement these things. That's it. Nothing more than that. So, uh, it's, uh, it will help, uh, little bit. It's it's costly for the phone number verifications. Yeah. In India, there is a a lots of services we can using, but in a flow is a fast implementation. Everything is easy to handle this thing. So so user experience for the implemented and, uh, suppose we need a, like, phone number then, uh, enter from the client side phone number then, uh, we can give, like, OTP then verify then, uh, we can make it make it API. Like, if OTP is same, then we can verify an account in a user, uh, user table. We can go like user table, and we can verify 1 like 1, 2, 3 like that's it. So it it's

Okay. So by crypt, uh, MySQL is okay. So, uh, normally, uh, you know, MySQL MySQL, uh, we have a database of MySQL. So, uh, we know how to, uh, implement it, like, a sign up, uh, like, once we can bring, like, a sign up, then, uh, there is a password, like, the starter. But we can we can convert it in a bi crypt. So bi crypt means, like, uh, it will, uh, it will combination of the has, uh, hassing, uh, hassing. So it will come running, like, a has, uh, has levels. So, like, nobody can, uh, understand like that. Uh, nobody can, uh, like, taking from the actual or or actual converting in a SIMP. So, uh, use of JWT use of JWT and, uh, JWT, we can suppose sign in then, uh, password. Uh, we can encrypt it. Suppose by crypt, there is a one package by crypt. So by crypt, we can install, and we can converting in a, uh, password in a by crypt. Then we can insert it, uh, inserted in a MySQL level, uh, by crypt method. Whatever by encrypt, we can do by encrypt, then that's simply can, uh, we can, uh, we can, uh, adding in a, uh, in a d b, uh, in a d b level. That's it. So this, uh, by encrypt, we can we can say, like, uh, not we can store in, like, actual data. Like, suppose password, there is something like also, like, like, uh, I know on bitch. You add the red 123. It's up my password. So we can encrypted these things. Uh, help of by creep. Yeah. There is a encryption, decryptions, uh, like, uh, encryption decryption method in a, uh, node. So we can, uh, we can converting these things in a, uh, level. Then if we got that by encrypted, then we can directly insert it in a d v level. If not, then we can before that, we can encrypt using, uh, using, uh, like, bike, um, bike rip package. So we can insert it like that. So this is the main approach we can bring these things. That's it. So anything, I think, uh, by this is a approach where we have to doing, uh, like that. Okay. Yeah. So, uh, we can tell, like, uh, as according to coding level. So, uh, Bicrypt, we already tell, uh, told, uh, like, Bicrypt, uh, one one type of package. Then after that, we can, uh, install it. Then suppose we are taking from the, uh, any password level. So, uh, there is a one method, like, uh, we can select any processing salt, uh, salt round, like, biclib.has has and password. Suppose, uh, any any variable you can, uh, give you, like, how much length? Suppose, uh, 5 to 10, yeah, 10 to, uh, 20. So there is a what type of length we can provide it? Suppose the blackberry dot has, uh, password or whatever password coming from the, uh, API. Then after that, Salt RAM, then we can keep it. And then after that after that, we can insert these things in a d v level. So that's it. So these are, uh, method of MySQL, uh, using by crypted method. And in a d v level, you can we can also, uh, MySQL as a not like a integer, like, uh, not and begin not we can we didn't do this, uh, because of it it's not holding a length. So, uh, we can insert it as a that, uh, these things. That's it.

So, Okay. So, we can implement it like, uh, suppose as as per my example, uh, suppose there is a one table user. So, uh, firstly, uh, firstly, how much record we can, uh, find out, like, suppose there is a, uh, like, a thousands of record. But we cannot display, uh, in a in a level wise, uh, in a same safe pages. In a front end side. So we can using, like, a presentation. So we can send, like, page. We can set page and limit. It means, like, uh, in a one page, there is a limit. Means, like, a limit, there is a 10, 20. In a one time, uh, it will come, uh, it will come, uh, like, a limit, uh, 10, then 10. Only, uh, it will sort 10. After that, a physical one, then we can we can provide, like, a d v dot users find and count all. There is one method, find and count all. And building in a query level, we can we can implement these things. In a one time limit, we can pass this, and page we can pass this, and a page we can pass this. And after that, uh, we can say, like, a skip method also. Suppose, uh, 10 data already we can show. So after 10, uh, page number 2, then skip method, we can doing these things. After skip, then another 10 record will come. After then, uh, page is gonna 3, then after that, it will it will come. So there is a syntax in a way clause. We can say, like, a limit, uh, we can say, like, a limit, uh, limit, uh, semicolon, like a, uh, like a limit then. We can say, like, uh, a page, then we can provide the pages. And, uh, these are, uh, many approach we have to doing, like, uh, that one. And skip method, we can say also skip because of 10 record is, uh, uh, firstly first, uh, Tendergore, we can skip. Then after that, Tendergore, we can, uh, giving that. So this is the approach, uh, we we have, uh, doing, uh, like, in a Node. Js, uh, using the MySQL help of that's it. So this is the, uh, approach of the vision essence in a MySQL we have to use it. So, uh, another things, uh, we can we can we can, uh, we can we can tell, uh, suppose of auto incremented, uh, yeah. There is a one type of page. Suppose, uh, millions of data, and how it will, uh, it will, uh, it will throw in. So, uh, there is a, uh, one one method, uh, also, um, suppose we can select a limit. Uh, we can select limit page, and one is the we can say, like, skip. And according to, like, that one, uh, MySQL, there's offset method also. Offset method, we can provide it, like, a, uh, page minus, uh, we can select a page minus 1 into limit. How much data it we can show in a, uh, like, uh, front end side. So this is the approach, and we can also, like, we can say, like, some type of query and d v dot user find, uh, d v dot, uh, d v dot, uh, support user dot user is a collection name. Yeah. Table name, call it, users, find and count all. So all those things you can provide in a query level. That's it. Yeah. Uh, Yeah. We can say, like, a limit and offset, you can provide especially in a, uh, MySQL level. Limit suppose, uh, 10 and offset is called to page 1. 1, uh, into page 1 minus 1 equal to, uh, like, limit. So how much data it will skip here through. So this approach, we have to doing like, uh, that one. Uh, these three things we need we need from the frame to side limit, uh, limit base, and, uh, offset method. So offset method, we can calculate, uh, only limit and base coming from the frame set. So that's it. So these things are

How do you ensure okay. Endpoint developed by express are strongly type to 1 using TypeScript. So mainly, it's, uh, express, uh, dot g s. So we can using, like, a a TypeScript. Uh, so, mainly, uh, in a TypeScript level, uh, we we can passing, like, uh, input output operations, uh, uh, in a typescript level. Suppose, uh, we are sending, like, a which type of type function we can sing, like, a, uh, suppose. So there is a we can we can passing, like, a, uh, 3 parameter. In a typescriptor using x-ray.js, we can pass it 3 parameter. Suppose ID, we can we can select ID pass, uh, we can set query pass. Now we can say, like, integer pass. So if ID, then we can ID semicolon in a in a parameter. ID semicolon, uh, like, integer we need the number. And, uh, suppose, uh, query then we need a string we can pass semicolon string like that. So this is the approach we have to doing, uh, express uh, express dotjs r s from it. I'm using using the typescript method. So this is the approach we have to doing like that. Okay. So, yeah, uh, according to, uh, TypeScript also, it's a function level then suppose we can pass in a app dot get. Uh, in app dot get method, there is a request parameter, request response, and next. Then we can say, like, a request to semicolumn request. In a above the, uh, importing once we are importing in a request level, so we can we can say, like, uh, request response, and next means it's a function. So we can, uh, say, like, a p app dot get. We can as example, uh, app dot get. Uh, there is a method we can passing, uh, like, uh, like, uh, we can select a semi semi column, uh, or not semi column. Uh, we can break it, uh, slash, like, support user and list. So after that semi after that comma, then we can pass request, then request, semicolon request, request full. Response res semicolon response. Then suppose next then semicolon functions. So that is the approach we have to do in these things. Uh, yeah. We can say, like, in a DB level, uh, suppose you can or DB level, we can say, like, a main brand main file. We can implement app dot huge. So there is options, sir, or suppose error. So what what is that error means? Error, uh, semicolon. Any means like anything like number number, uh, string type of anything we can display. Request semicolon, uh, iq, request and requested, uh, request you can say, and respond that requested. And next function. So after that, we can say, like, a console dot error, then whatever error we are getting that, then we can print it. Something like break. Yeah. So this approach, we have to bring these things. Yeah. We can maintain, like, a type status. Suppose active, yeah, inactive, yeah. We can say, like, interface maintaining, interface ID name, uh, status. In that case, uh, these things we can maintain in a typescript using, uh, help of, uh, express dot

The best approach of manage and apply conferencing. It cost more to environment. Any notice? Beautiful environment tree. What is that? What is the best approach to manage and apply apply configuration manage? It goes no. Just So, uh, mainly, I have used, like, uh, environment like a dotenv files and maintaining any file. All those things so whatever we have to needed, like, suppose uh, port number we can define in the port number there in in like, uh, dotenv file dotenv file. And, uh, dotenv file, you can maintaining, like, a port level, then everything uh, suppose, as example, suppose, whatever need suppose, uh, because we are not taking from the any files. So configuration level. So you can take it from the environment level. So, uh, local local then we can define this thing with DB host and, uh, like, uh, port number, then port we can define in environment level. And all those things, whatever need, uh, we can define in a ENV file. Then we can take it from there, process dot next process, uh, process dot next dot ENV. So after that, we can take in all those things data in a, uh, anywhere, uh, in that applications, uh, like any controller host, uh, services. Yeah. Any files, we can take it from there. So, otherwise, another process you can doing, like, these things configurations levels. So there is a one file we can define, like, config dot JS. And all those things we can also define there. But it's not secured, uh, because we can push the code, then it will go in a, uh, like a server level. Yeah. We can say like a, uh, we can say like a, uh, like, a git in a git. So this is not a good approach, or we have to bring, uh, like that. So we can everything maintaining any ENV files and ENV configurations, because of it will, uh, secured. And, uh, otherwise, we can bi crypt it also. We can another method is a bicrypt it. Because any data, uh, coming from the, uh, EME file, then we can buy crypted. Because of sometimes, so we can, uh, we can, by mistake, uh, we can we can throw it to the client all those data. So it's not encrypted. Then it will, uh, it will easy to hack that data and, uh, it will, uh, do anything. So that's why we can, uh, one method is a ENV file. Everything we can maintaining. Second one is the we can we can say, like, a configuration for the configuration level. So you can maintaining in a all those that are as a by crypted, uh, in a, uh, front end side. So after that front end side, we can also, uh, uh, suppose we are using, like, a data, then we can encrypt all those data. Suppose we can, uh, send one to another level, so we can pass, uh, all those are in a in a, like, a network file, uh, in a browser network. So you can train this thing. So these are many approach we have to doing like that, uh, configuration as well in the files. And if we know, uh, it's not secure, uh, we can we can do, uh, like, config dot j s j s files. We can maintain these things. And all those data, we can maintain in a main, um, index dot j s file. So all all before the all those component, yeah, we can say, like, a services, controller. Yeah. So commending these things in a level. Yeah. That's fine.

Yeah. Uh, potential issue, we can say, uh, first of all, uh, one is the 3,000 we cannot declare, uh, directly here. We can take it from the environment files, .nv files. So another one is the, uh, it's not synchronous, because of we know, uh, uh, we know, uh, we know, uh, like, node it's a only asynchronous operation we can handling in a so, uh, with help of, uh, async await method, we can doing these things. And another one is the, uh, async await method. We can one type of function we can, uh, generating like that. And after that after that, we can maintaining try and catch. Because of error handling, we need that most of important work in a error handling. So try catch, you can implement it for this particular particular code. Because of suppose we don't know how, uh, suppose, uh, so many so many traffic will come then it will broke. Sometimes it will broke. So we know, uh, it's a one type of design pattern, circuit breaker. Because of it will maintain, like, a, uh, network part. Mainly network part. So, uh, that case is, uh, we we have some issue. Uh, it's, uh, like, uh, only, uh, few traffic, then it's fine. But in a habit of traffic, then it will it will generating error. So in error, it will not help to the, uh, like, debug, uh, like that one. So we can using, like, a firstly, async method. Yeah. New promises, we can say, like, um, yeah, async only. Yeah. Otherwise, we can, uh, we can, uh, we can inside there. Uh, we can using, like, a try catch method. Error handling. Yeah. In a middle layer, we can handling these things. So these are main approach we have to do, uh, these things in a socket dot I o because of its it's, uh, it's a heavy, uh, load coming from the like, because of its socket level, we can, uh, real time data within that particular. So in a real time, everything we can move, uh, receive, send, receive, send. Then it will, uh, creating some type of issue. So issue is a only, uh, error handling. We can maintaining error handling for here and, uh, So that's it. So these things in my mind, uh, I have to do, uh, firstly, before that, uh, we can, uh, some line of code, we can, uh, we can generating. So EME file, we can maintaining firstly. After that, we can maintaining async await without track as method, which is error handling. If we are any, uh, CloudWatch. Yeah. Anything we can handling these things for that particular. And, uh, assuming we already told and try guys. That's it. So this type of method we have to, uh, handle these things for the particular reasons.

Uh, firstly, what are the patterns? What are the centralized? So can you select? So, uh, so, uh, for the for the particular patterns, we know, uh, we we can maintaining, firstly, uh, in express dot g g g s, uh, we can we can maintaining our main main, uh, files. Suppose there is a one type of file index dot g s. So we can maintain, like, there's a lot of proceed dot on method and, uh, unauthorized, yeah, unauthorized on handling, we can define there because anything we know, uh, error then we can define these things. And then the one is the centralized method. Centralized means like a as a middleware level, we can we can maintaining centralized, uh, middleware level we can handling these things. Suppose as per my example, suppose one type of function we can generating, uh, in the middle level, uh, middleware level, suppose, uh, function is error handler. So we can we can select a status code, everything we can define, and, yeah, message whatever message we are coming from there. We can message them. After that, we can directly respond. Uh, send. So export. Uh, one type of common file you can manage central, uh, centralized middleware labels. So we can define everywhere. Uh, if nothing to find, then we can define directly this thing. Anything we can display. So after that, there is a custom error class. So we can we can maintain in oops. We can flow the oops. We can use the help of tap script as a tap script. So you can maintain any type of, uh, classes. So, uh, whatever status we can define, so we can directly throw the message. Proceed on method, and we can define there. So another means the error handling, uh, like, we can mainly also routes levels also. Whatever routes, uh, they are coming. Yeah. Whatever do, uh, it will come. So these things, uh, structure level and, uh, secure method, we can sing like a try case method. We can using, like, normally normally, we have to using, uh, async, uh, async await method. We have proceed on proceed on. We can select, uh, a better user, like, a error for the particular errors. So this type of method, we can, uh, implement it in xfinity.js for the handling error. So, uh, there is a different patterns. We can say, like, a centralized one type of pattern, a middleware patterns, all it's all including a design patterns. So this is a part of, uh, uh, being like that, uh, like, async error. We can select a async method. Also, we can use it sometimes. So the sometimes not. Uh, async error, we can select a, uh, suppose one type of function, we can maintain, like, a promise letter result. If there is a error, then we can, um, we can throw the error. Otherwise, in a catchment, we can provide it. So and less thing ops option also. Logging type of also, suppose in a, uh, node just I have used CloudWatch and with some for log logging errors. So when storms, we can select a this time, we have to doing like that. So, uh, this type of, uh, method we have to using, like, in in environment level also we can be using, uh, handling. So mainly, these things, uh, we can select a centralized level, um, error error handling level. Yeah. I think, uh, logging error, we can say cloud and windstorms. And another one is that we can select a implementation error and custom errors. We can say classic.

What the ports do you take? Migrate to computer database skin count on. Conflicts. Cancel it now. Conflicts. Uh, we can say, like, uh, downtime. So, uh, in my approach, uh, so first of all, uh, we can we can migrate it. Uh, we can migrate, uh, these things, uh, in a type r m using a help of type r m. So, uh, firstly, we can, uh, replica. We can we can maintain replica. Uh, suppose a one t 1 d b, sort of, like, downtime, then another automatic, uh, automated transfer to the another d b. So one, uh, this this approach, if you you are using a coding level, um, we can, uh, we we we we can select a support type of RM. So there is a some some type of approach, uh, we have to bring like that. Suppose, uh, we need, like, a, uh, migrate interface, one type of migrate interface, query runner, and table column, whatever table table column in a type ORM. So these things, suppose we can select a migrate, uh, interface level. So we need some type of, uh, code like a suppose, uh, as per, uh, as per my, uh, I don't remember, but I know few thing few line of code. Uh, I can explain, like, suppose there is a one type of, uh, parameter. Suppose you can pass the migration interface. Yeah. Query run runner. Then we can we can say, like, a query not a query runner dot add column. We can say, like, uh, whatever table. Suppose if there is a user table and table column. Which table column we can modify, uh, we can bring like that. So name type and is nullable or not yet default, whatever that. So, uh, if if there is a downtime mode type, another function we can creating, suppose, uh, downtime. And inside there, we can we can pass in a query runner and approach that, uh, query run, then we can drop, yeah, anything. We can do anything. Yeah. Data migrate, we can see suppose, uh, that data we can storing. And after that, we can, uh, we can modify the table here anything. So can import it that that, uh, that, uh, things we can bring this thing. So deploy so this approach we have to, uh, we have to do, uh, in my in my case. So I don't have a lots of migration knowledge right now. So one of these things we can we can do, like, uh, some line of code we can modify, uh, implemented like that. Sure. That's it.

So, uh, so, uh, for this particular, uh, there's a multiple integration, multiple third party API. So there we have approach, um, API gateway. Uh, we have approach API gateway. So suppose we can define, uh, uh, there is a one type of, uh, API, uh, proxy our proxy for the API API gateway, we can in integrate for the particular or multiple third party API asynchronous operations. So we can do, like, uh, proxy patterns, uh, proxy patterns. We can select a proxy patterns, uh, in a design patterns part of design patterns. So one type of proxy pattern, we can implement it for the API gateway. So, uh, install proxy, uh, one type of express, uh, express, uh, express proxy, uh, one type of package. So we can install them. After that, we can, uh, we can constant proxy, uh, require and, uh, express a proxy pattern. The this line, we can import it. And after that, we can, uh, we can, uh, add that use. So so in a add that use, we can we can resolve multiple third party integration. So we need a, uh, like, a gate method or a post method, whatever method, uh, we have. So, uh, so, uh, we can define proxy and URL with URL. So after that, we can call these things in our applications. We can maintain, like, one type of functions, async await functions. Yeah. The promises functions, and inside, there is async, uh, support async and user list. As example, user list. Uh, one type of part, uh, one one type of, uh, sign up for the 3rd party. Uh, async, uh, user, then after that, we can define everything request response, uh, in a task screen method, a request, uh, and semicolon request and respond them responses. So that then after that, we can we can inside their try catch method, we can implement it. After that, then we constantly, uh, user, uh, list suppose away to you, uh, from there. Uh, we can we can using, like, uh, we can call that API, uh, API gateway. So, uh, method what of data we can get? So we can, uh, getting response. And there's another method also, uh, adjust or with help of adjust thought part integration, we can, uh, using adjust also method. Adjust method, uh, we can directly call whatever URL coming from the whatever, uh, URL and get post method, uh, adjust dot get. Yeah. Adjust dot post and URL, uh, comma then, uh, whatever payload we can sending. So we can maintain one type of object, uh, we can maintaining. Then we can throw the adjust level also. And if they get to, we can need a proxy level. And if another thing, if there there is a heavy traffic coming from that particular API, so that particular third party, so we can maintaining, like, uh, we have options, like, SQS. Yeah. S n SQS, uh, Kafka, RabbitMQ, queue operation can doing, uh, like that. So we can maintain all those things we can maintain all those things, uh, help of, uh, Kafka, RabbitMQ, and SQS, uh, for the message broker who can be using, uh, normal CCA. Yeah. Otherwise, API gateway. Yeah. Help of xios. Whatever, uh, whatever, uh, traffic coming from the, uh, whatever traffic, yeah, uh, coming from the, uh, that particular API, so we can maintain these things. So so, uh, this is the main approach we have to do in Lyda. So that's it.

Yeah. Same things. Uh, how do you handle challenges, strong tabbing, uh, when integrating in external API like tab? So, uh, there is a cover like a Luzhi capalsal, uh, capals like that of, uh, uh, method. So we can use the same things API gateway for the API gateway proxy patterns. So we can flow the proxy patterns here. Any message brokers any message, uh, message broker we can using for for that particular, uh, assume typing integration. Okay. So, uh, it will not fail because it will it will, uh, help up these things. Um, multiple API, we can integration. Already, we can integrate it. Uh, so typescript, uh, help of typescript. So we can we can train the in a method level. So what a parameter we can passing like that. So these things, we can maintain. We can select, uh, as in crunch operations. We can maintain these things. And, uh, that's it. Uh, nothing we can help out, uh, or any message brokers operations like mess message queue, message, uh, any queue level, revenue queue, yeah, Kafka, anything. We can implement API gateway API gateway. We can select a proxy patterns. We can follow that. Yeah. We can use it like a adjust method. So same things, uh, we can select. Uh, that's it. Nothing more than that.