Shrey Prajapati

Hi. I'm, uh, technology manager, uh, with a 15 years of experience, uh, like in leading and mentoring the team, uh, for delivering, uh, impactful and, uh, high valued projects. I have managed 20 to 25 members of team, and, uh, I also deliver complex projects like an ecommerce, real estate management, and e some of the ERP solutions also. As a technology front, I have worked with, uh, cloud technologies like an AWS. Uh, in AWS, I have worked with the, uh, RDS, Lambda, uh, EC 2 instance, VPC, and, uh, s 3. And, uh, if I talk about the specific, uh, data engineering services, then I have worked with AWS, Blue, Crowler, uh, Athena, Amazon, EMR, and, uh, Amazon QuickSight. And a little bit about, uh, I have worked about, uh, Amazon, uh, managed Apache Kafka, uh, and, uh, streams. Uh, apart from this, uh, as a a profi in a programming language, I am working with the PHP Python and the front, uh, like, a a front end frameworks like Node. Js or JS And Express. Yes. Uh, if I talk I have also worked with the big data technologies like in, uh, uh, Apache Hadoop HDFS, Apache Spark, Apache Flink, Apache Superset, Apache Hive. So, uh, all of I have worked with the different, uh, versatile technologies. And if I talk about the, uh, like, uh, in all of this product, I always follow some of these, uh, and software practices, like in, uh, like, creating a property retrenching and, uh, are deploying the projects using, uh, like, CACD pipeline. And to maintain the CACD pipeline, I have used the GitHub, uh, GitHub accents, uh, and Jenkins, Kubernetes, and Dockers. And, uh, I'm also contributing in the, uh, client common distance. Like, to discuss with the client and particular stakeholders to convert their, uh, business department into the solutions. Uh, also, I have due to my experience, I have also involved in the appraisal activities, like, to discuss with the client, uh, to give a proper, uh, technology strategies or, uh, giving a proper, uh, suggestive approach to them. And, uh, yes, you can consider overall, uh, I'm, uh, uh, like, very, uh, are are driven by, uh, I'm driven by technology. Uh, I'm very passionate about the technology. Thank you. Thank you very much.

Okay. So here, the best, uh, uh, example is, like, to set up the proper archit branching. Uh, like, normally in normally, in a project, we are setting up the deal, uh, staging, and the products environment. And from the open branch, always, we will prefer to create the feature branch. So I will prefer to create a different feature branch. So suppose I am working, so I will create my own feature branch, uh, with with, uh, with particular my name. And if the other developer, uh, has, uh, created, then they will upload that, uh, that particular branch. So which I can easily merge that branch, and, um, uh, like, my branch will not be updated.

How do you do how do you manage the state? So there are multiple ways to, like, uh, storing, uh, this stage, like, in log normally, in log in, uh, state, normally, we are using the, uh, law either local storage or cookies. So what we can do, suppose if there's an, uh, uh, suppose suppose, uh, a question was answered, then I will store that particular things in our local storage. And, uh, like, uh, showing that one, there is no need of refreshing the browser. Uh, right. And, uh, also, like, cookies is also, like, uh, also on on those solutions. In cookies, we have an extra facilities like, uh, uh, we can store that at a particular time of, uh, up to up to particular time. For example, if you want to store that data, uh, for the specific, uh, like, 1 or 2 or 10, we we we can get the facility into the cookies. But in case of, uh, local storage, yes, we can, uh, do that facilities. But to be able to maintain those, uh, that, uh, expire time, we, uh, according to our, uh, logic only. Like, we have to have every time you have to calculate it, uh, time is expired, then you have to clear those, uh, local storage. So this is the, uh, options. Like, I'm I will, uh, suggest the login state, uh, reading the answers, questions in the form of the re refreshing the browsers also. Thank you.

So, like, in the symphony, while we are creating the APIs. Right? So first of all, we have to keep the proper standards, like, and, uh, we have to, uh, create the APIs, like like, uh, like, uh, within basic ground and list of persons, like create update early, uh, delete, and, uh, list it, uh, that list APIs. And we'll always be able to follow the proper commenting for that particular, uh, uh, every, uh, list APIs functions, like, uh, like, maintaining the proper commenting. So that while deploying, it will be automatically helpful, like, uh, with the tools under the our documents accordingly. Uh, so in if I talk about the, uh, like, deployment strategies, then what what I I can consider in this one. So I will suggest, uh, in the application, uh, if you if you deploy this, I have a presence in the Kubernetes, then right? So I will always, uh, refer, uh, uh, we can send rolling update strategy so that if we will update the fee, uh, update that feature, so it will not, uh, like, down, uh, it will not down the, uh, like, of auto current running. If our new features will be uploaded, once it is uploaded in particular one port, then that, uh, that previous node, one node was the down. So, like, I I will I will prefer the, uh, rolling a bit, uh, strategy in this case. And if my future is very, uh, like, uh, big, it will change in a very, uh, large database or something like that. Then what is I I will prefer, uh, like, a blueprint strategies. So in return, I will create the identical, uh, one of the environment, uh, where I will deploy that, uh, my API. I will test it. And if it is working fine, then, gradually, I will, uh, using them, uh, like, in this, I will transfer all my load from the, uh, like, blue, uh, like, open blue environment for to the green environment. So, yes, I will use, basically, this type of, uh, strategies like, uh, rolling update or a blueprint deployment.

So so, yes, in this, uh, PHP based applications, what we can do, uh, we can create, uh, we can say it's a separate, uh, open module, uh, and, uh, we'll create a separate database for that particular in that, uh, for that particular module. And uh, what we can start like, it would be like it's a high level example. Uh, suppose if you if I talk about very, uh, like, I have usually work with ecommerce. Right? So in ecommerce, we have a product model. Uh, we have a I mean, customer model, product model, and, basically, we have an order model. Right? So what would it be? We'll create, uh, 3 models and the 3 separate, uh, we can say it's some database for that particular things. And suppose, like, it's there is 1 page, like, where I need to display, uh, like, uh, the orders generated by that particular user. So I need to fetch all those orders, and, uh, we can set some, uh, item detail. So what I will prefer, uh, in this case, I will use, uh, to maintain a separate one. Uh, we can say it's on a module only. And, also, I will keep the separate database for that one. So what I will do is, uh, when whenever anything, like, customers will register or any product will be added or any orders will be added, So I will use any, uh, like, uh, messaging queue systems, like an either a a RabbitMQ or an Apache Kafka or, uh, we can say it's an any other, uh, like, uh, messaging services, or we can create an event was also. Like, we will send that. It means we will push those events into that particular messaging services. And, accordingly, uh, as a receiver, uh, in this one, uh, we will sync, uh, as in we will, uh, either a, a hook or something like as an event. Uh, in this particular, uh, like, uh, this 4th model, uh, once we'll receive the, uh, event, uh, I will create the database accordingly, like, uh, customer, then order ID, and then item ID, that item name, something like that. So I will, uh, as a combinations of all these 3, uh, modules, I will create a separate database so that, uh, if the 3 services will be down, then also my default services will not, uh, like, have any issues with that, uh, other down, uh, down services. So, yes, I can use these microservices architectures, uh, like in the PHP based applications.

So, uh, first of all, the first issues I can identify, uh, we have used that async function. So while we are calling the fetch, we have to use it await, first of all, in that one. Also, as a coding standard, uh, like, we are, uh, just concatenating the string. So as a coding standard, we can use the, like, back tick, and we can use the proper string on only so that the user ID will be is a written. And, uh, also here, uh, uh, we are directly doing, uh, like, response to JSON, and then directly, we are doing the console dot log. Right? But here, in the return statement, we are returning the, uh, particular, uh, like, as a, uh, string only. But instead, uh, the data, uh, that should be, uh, written into the, uh, uh, function. So, well, like, I have been I I can consider the measly 3 issues, like an await, first of all. Uh, then, uh, if you have to, uh, use a proper as a coding standard, you have to use a, uh, like, string to, uh, in the 5 statement, the 1st APS slash user, uh, slash 10, uh, as in dollar, uh, dollar user ID as in old string. All and, also, in the return, we have to return the data itself. Also, if I talk about any, uh, we can say, uh, as an, uh, error handling. Then here, we are not handling any type of errors, like whether whether they whether we are receiving the data or not or something. So we can do, uh, we we can also integrate the like, try and catch, uh, our concept also so that, uh, uh, like, anything happens, like, uh, into this API or something. So if we are not getting proper response, suppose that API is having some issues and instead of, we are receiving a text so that the second statement that then response response will be are not work. So instead, what we can do, we can use an, uh, like, either we can say it's promise resolved or try and catch, uh, error handling cases.

If I talk about the web securities, then what we can say, as an authentication system, like what happened, suppose the user is already logged in, then what we can do, we are storing whether like access token, sorry, in JWT token or something. So if you will send any of the request to fetch any of the data after login, like for example, if it is a shopping cart, then I find getting the users, for example, users order data. So if I'm calling any of the APIs to fetch those data, so I will send those, the token also and at the API, I mean at the server end, I will cross verify whether the token is valid or not. If it is valid, then I will send those data to that particular front end. If I talk about the network security, then I will use the SSL always. So that in the transition also, there will be no changing the data. And suppose if you're not using an SSL, then also there are some mechanism is available. Like when we send the data along with the token, what we will do, we will calculate the checksum. So checksum is basically like whatever the data which we are sending to the back end. So we'll make them in a sending order, we will make them in one of the pattern, and then we will generate one like using the, whether we will generate one SH token. And similarly, once we receive the request into the server end, what we'll do, we'll again, we'll fetch those data, we'll again do the same calculations, like we do the same process like proceeding, like doing the sorting of this particular data, creating the checksums and we are comparing those checksum. So that if the checksum is proper, means there is no change, there is no possibilities in the changing in the data. So yes, like this one, we are like handling the like securities in the web applications. If I talk about like entering the data, right, so we will always use a proper XSRF token, so that there is no any directly DDoS attack or something like that. Apart from that one also, like we are not, means always we are doing some sanitizations in the data. For example, in the first name, suppose if you enter a script, alert1 script close, then that not be stored into our database, otherwise what happen, where we are displaying the first name, in that case it will be alerted, why, because it's like script tag. So what we are, normally we are sanitizing those type of data also, and most of the framework that is like, this type of filter is available in many of the frameworks, like in Codeigniter or Laravel or Symfony.

In this one, what we can do uh, in this one, uh, the first, uh, what I'm seeing, that one has a solid principle. Uh, the first is like, whatever, uh, our, uh, implementation is there. That should be a single responsibility. Right? So here, if I talk about them, this this is a, uh, like, process payment. Right? So if there is if it is regarding the payment, then the whole class should be, uh, that should be available for the payment itself. But here in this, uh, processing payment, we are also calling the shipping method. It's initiating the shipping method. So that, first of all, that is the, uh, we can say it's an one type of, uh, issues is there. Uh, also, uh, if I talk about their, uh, so what we can say, it's an open for, uh, where there is an a second visible open for extension and, uh, open for extension, but and, uh, close for the modification. So suppose, for example, if I if there is any change in the, something like that. So so if it is a message message data things, then it should be, uh, like, I need to extend those message data things. But here, what happened as the code is available into the single class itself, I have to open and update that particular payment service class itself. So the also that is evaluating the, uh, like, uh, the second, uh, we can say it's a principles like open for extension and closed for calculation. Uh, if I talk about here other issues, then here, basically, what happened, like, after if I talk about all the procedure here, what what actually it is happening. So here, what happened? Uh, we can set some payment processes. Right? So after here, we are calling on funds, and there is a process uh, process payments after processing the payment. Uh, what happened, it is returning, uh, one flag, whether it's successful or not. If it's successful, then it is calling. It means it is sending that, uh, in messaging that you, uh, the dispatch where the payment is successful. And, uh, it will sending the proper, uh, one of the order ID. And in, uh, if it is successful, then and then they are initiating the shipping charges. I mean, ship initiate the shipping. Right? Because, uh, right now, it's a it's a failure, then they are saying, okay. Uh, the payment is failure, and, uh, this is the order ID. And, uh, as this is the failure, uh, we need not to, like, uh, initiate the shipping method. Right? And, also, in the shipping method, uh, uh, what you are you are checking is this is whether it's a physical product or if it isn't, uh, digital product here. If it isn't shipping product, then shipping will be initiated. Uh, so here here and if it is a busy, uh, maybe it is not a, uh, physical product. You can say it's a, uh, like, another product. We can say it's a subscription or digital, uh, digital subscription or something. So that may be a possibility. Sorry. So in that case, we need not to do any, uh, physical delivery. So, uh, the that else part is in that, uh, then there is a, like, shipping not required in that case. So, yes, this is oral, uh, under the, uh, um, the method the class is specifying.

So, yes, in like in a single page application, it does not mean like we cannot like go to another page or something, but every framework like providing a proper routing mechanism, right? So we can create like for example, if I talk about the react, we usually have worked with the react. So in that react, normally we are like we are using the next framework, right? So in that next framework, we have a path-based means as in file-based routing. So for example, if I talk about like it is in profile section, so in profile and then edit profile slash edit profile slash show profile slash list, something like that. So what we can do, we can create the different files for the particular profiles and we can create a particular component for that particular pages so that like when we are navigating using a different, there is a links, link component is the default component link. So link.navigate. So if you'll navigate, then it will not refresh the page. So in the internal using a routing mechanism only, it will just clear the component, current window component and it will like, it will mount the another component which is according to the file-based routing. Also in case of core react, so in core react also we have a routing mechanism is there. So we are like, according to the different route, we are changing the URL and according to the URL, the component will be automatically changed inside the front-end framework. So yes, according to that means we are based on the routing and based on the different frameworks like as I discussed in the next framework, we have like file-based routing. So using that one in the, like we can maintain a multiple pages, a single page application.