Nishant Kora

Could you help me understand more about your background by giving a brief introduction of yourself?

Recording purpose. Describe the process. Hi. Uh, describe a process to incorporate a diverse base development environment for Django application, uh, ensuring alignment with the production. Describe a process to incorporate a Docker based development. Um, and, yeah, Docker based development and operations and showing alignment with the production. So, um, first, uh, we need to, uh, create a separate configs for each one of the environments initially. And, uh, as we have a Docker based replication, then we need to create a separate ports or a separate, uh, ports for each one of them. And, again, first, we could need to create a Docker file, uh, which will contain separate for each of the environment for our for development, for staging, and for the production. Um, and, uh, once the development and monitoring are productions, then we need to create a segregation's Docker file for each one of the apps, uh, for the Docker based applications as we have our apps. Inside our Docker project, we have our apps, um, like, uh, each separate separate app should have a separate Docker environments and should have a separate one environment. Either we go that with that approach or keep the separate environments, files in a separate repository. Um, so then, uh, we can use the individual things. It could be deployed on the Kubernetes using the separate segregations of the files.

Setting with best practices. How would you manage a session state in load balance? We have to place an interface in which trying to go back in. Session state. It's doing the best practices. How would you manage your session state? The first thing, the load balancer, what we have been used in a React app is like a stateless approach used for storing the session data, uh, like a Redis, which can be accessed in all the back end servers, um, configuring Redis to use the state. And even that Redis also can be used, um, inside our either um, we can use a session state inside our engineering's application, um, or else, um, we can even use a load balance inside our engineering's applications where the applications the request will be coming based on the, um, like, assess like, a a load balancing strategies. So we move ahead the requests here and there. And, again, otherwise, then, uh, we use our release for just a temporary kind of storage. Yeah. This is how we can use a session state, uh, for managing the React application. Even we can use some kind of React states, uh, where React states where the application could be stored temporarily. And for Django back end, uh, it will be maintained a session at the application level itself. Yeah. This is how it should work.

How do you optimize an extra JS application? Load time utilizing in SSR feature, particularly for data heavy pages. Uh, the first approach, uh, where we can use using the efficient catching strategies, uh, where we can optimize it, uh, then we have get server side box to fetch data at the request time and, um, delivering a prerender HTML pages to an client, which improves initial load time and an SEO. Other than one more approach where we can keep the load packages compiled, um, each time so that application will be loaded faster. Then, again, uh, might be, uh, whenever we try to we can use a a catching headers, um, in order to leverage some repeated data, fetching frequently excess data. And then either then we can minimize the load time of an API so that the initial load or, like, the application will be utilized very fastly loaded. And then we can have an paginating or an, uh, loading the data lazily. That is another kind of an upgrade, then we can have a CDN caching, uh, um, instead of loading the data there, then we can use the data from a caching technology, uh, that where the data will be stored in the CDN at a particular specific servers. This is how we can use, um, for, uh, optimizing the for data heavy pages.

Can you describe a strategy to effectively manage a state? Can you describe a strategy to to your manager state? Because some of the clients in the context API and the hooks. So we can use, uh, reducers within our providers to a complex state logic, and then we can use the access states by using the use context in any child component, uh, by reducing the prop billing. And we can create a custom hooks for repeated logic, and then we can make a use of, uh, code modular and the reusable ones. Um, then we can use a react memos and use memos to prevent unnecessary re renders, and we can even split the large context to our unrelated components rerendering. So with the rendering, it will be done very faster. Um, Yeah. This is how we can, uh, work on it, uh, for managing the multiple states across the AI component utilizing context APIs and hooks.

Consider a high traffic web application. How do you ensure database read and write operations? Considering a high traffic web application, We do ensure that it have read and write operations in postcode, maintaining the asset properties without compromising the performance. The first option for a high traffic web application is that, um, we can keep 2 separate databases. 1 is for read and 1 is for the write. Uh, all the application reads happens from a specific, uh, only the, uh, read database. And all the writes, uh, should happen to an another instance of a database, uh, where only the writes will happen, and the writes of the database should sync to the reads so that, um, the application will be much faster and there is no conflict in our read and write operations. Um, uh, so that, uh, then again And, uh, if we have a very, um, high rates or rights, then we can read the data simultaneously using across the read replicas. Um, then again and then we can use some kind of an indexing strategies, uh, use some kind of a binary search tree or all some specific kind of algorithms so where we can, uh, implement those things so that our indexing search can be much more faster. And even we can do a replication and even we can use a sharding strategies where the data, it will be read much faster, then we can use on a a repeated some kind of data or common data we can keep inside the caches. So with the data, it can be fetched very fastly. And, um, for bulk write, so we can use asynchronous processing. So where the data can be writes very faster for the large volume of data. And then we can distribute the queries across the different machines so that the workload, it can be reduced. So this is how, uh, it will look for high traffic web application.

Full stack engineers often so took a number of questions. 7. Okay. Full stack engineers often handle both server side and the client side core. Full stack engineers often handle both the server side and client side codes. The Django code snippets below, please explain what might be the wrong if the view function is not creating a new record in the database as expected. Please explain what might go wrong if your function is not creating the the database. Uh, the first option is, like, we need to check the logs, um, so that, uh, what is the kind of error, uh, we are getting it all so that we can go ahead and create, uh, like, check that errors, log errors, and just work on those things. Um, and then, um, we need to apply all the constraints, whatever it is requiring the database. Suppose, like, a primary constraints, uh, or the data, the value should not be null. Even those that is second kind of a check. Um, and if there is some kind of manual commit is required, uh, when those things are also we need to take care of it. And even we need to ensure that whatever record object we are creating, uh, make sure that the database model is being getting created. So these are the 4 cases where we can consider on it.

Uh, for a given Python code that enables restful API design patterns in Django, explain what could be improved for better scalability and maintainability. For a given Python code, uh, that would enroll a restful API design patterns in Django. Like, you want Python code that, you know, restful API design patterns in Django. Explain what would be improved for a better scalability and maintainability. Uh, so, uh, for better, um, uh, readability, So we can, uh, use a kind of a proper spacing and then a punctuation, uh, kind of it. So in order to read it very efficiently. And then, uh, we remove reading of unnecessary kind of data in the filtration so that our scalability can be improved. Um, and then, uh, we can paginate the things for a high scalability. Then we can cache as well. Filtering is the one, and the caching is the second second technique. And then keeping the view as a very lightweight by using the pagination. Um, then, uh, we need to do in kind of dependency injection for a security. And, um, yeah, these are the strategies where we can consider. So these are the strategies for better scalability and the maintainability and even readability as well. Um, and other than these things, then we can consider scaling the data, uh, by using the replication. So if many people comes, the data can be read very simultaneously on this caching. These are the things where it can be considered, um, for reading. So we can keep a 2 separate kind of servers. 1 is for reading and 1 is for writing. So whatever the load comes for reading, so it can be read only for only reading purpose so that there is no load on the server. As soon as we see that 80% of the data has been used for the servers, then we can increase auto scaling has should be enabled so that the scalability can be improved. And, um, so we can even segregate, uh, this among this class items at a query set and a serializer. As we have a create and a query set, we can segregate this into 2 separate classes so that even the readability is also much more easier. And even we can create some kind of an index on the database so that it will be read very much faster. Uh, even we can use some kind of, um, a raw, uh, raw query, uh, instead of that Django framework for fetching the database. We can use a raw query so that the data will be much more faster. So instead of serializers, um, even we can validate the data by using some manual JSON, and then we can, um, save the data without validating inside the serializers.

So how do you design a real time collaborative editing feature in Django based web application with simultaneous edits on, uh, PostgreSQL? How do you design a real time editing feature in Java based web application with simultaneous edit on PostgreSQL database. So edit. The first approach, uh, where we can use is, like, integrating the WebSockets for live updates, uh, allowing the clients to receive an immediate changes, um, then implement a concurrency control system to handle the simultaneously edits where each change is time stamped and validate it to prevent the overwrites, um, prevent the overwrites and even, uh, so we can see those time stamps and, uh, overwrites and just edits only the things, uh, whether it is required only for those timestamps. Um, and then, um, we can use our release for managing the state for a conflict detection and then, uh, as it supports, uh, like, real time. And then, uh, we can track a cursor in real time, uh, for the multiple edits as well. And, um, then we can use so one state, anyone, we can maintain it through using the ID, some kind of things, where we can track it down completely. And even through each IDs along with the time stamps as well, uh, so we can maintain its state somewhere and reading those states simultaneously in order for the multiple edits as well. Um, IDs in combination of time stamp and when it's time stamp. And, yeah, these are the things where we can consult on

Can you devise a strategy to implement advanced search functionality with filters and full text search capabilities in Django application? So, uh, for this one, uh, we can use an elastic search where we have an advanced search as well as a partial text search as well as full text search. So in, uh, Elasticsearch, we have an approach where we need to sync the whole data into an Elastic data Elasticsearch database. And whatever we use the strategies, then those things can be implement. Or other strategies, either a full text or search based on that one. Uh, the, um, Elasticsearch strategies will give us this one. And even, uh, we can go ahead with the search index where we can collect the search index on the database so that, uh, it will be very much faster. Um, then we can integrate some kind of, you know, filters. This is like an manual approach, uh, with some kind of, you know, advanced approach. Like, even we can implement some filters, like multiple filters can be introduced so that, uh, only those filters in that the query will be much more faster. Um, and then we can create some kind of, you know, search form, well, kind of filtration, and then we can have some kind of use in a database where we can filter those things. Uh, and then, um, we can even highlight the matches, um, to the matching keywords and the results that is equivalent to the Elasticsearch database. Either things, then we can keep it in a cache, uh, and do some kind of indexing for a faster search literal for optimization. Optimization. So what else I can suggest, um, is that, uh, it depends on the situations and then application needs and the requirements where we can design these things as advanced search will come with a multiple, uh, uh, facets. So, uh, based on the requirements, so we can go ahead on this one.

Uh, how do you ensure cross browser and cross device compatibility for complex CSS layout in response to React application? Do you ensure cross browser and customize compatibility? So, uh, we can, uh, use, um, some kind of an you can say, like, we can use some kind of an CSS, like a normalized CSS, some default standard sizes. And then we have flex boxes for the responsive designs or some kind of grid center flex boxes. So based on the things, whatever we mentioned there, so these flex boxes can be used. Then we have a media queries for mentioning the different kinds of a pixels and the width sizes. Then, um, then we can test on the multiple browsers. And even we have a different kind of portals where we can test on these things. Um, then, again, we have a responsive units like, uh, REM or a percentage, or then we can view view view ports or, like, view height and view width, something like this kind of things where the size, it will be automatically detected. Yeah. These are the strategies where we can use for the cross process sign, the, uh, and cross devices for a complex CSS for React applications.