Akash Deshbhratar

Okay. Yeah. So, hi, my name is Akash, and, uh, I'm from Nakkumar Astra. So, basically, I got 7.6 years of experience in Ruby on Rails. Along with Ruby on Rails, I have hands on experience in front end technologies also, like JavaScript, jQuery, frameworks like, uh, Angular and React. I have good, uh, hands on knowledge, uh, in origin control system like it have with. I worked in application domain such as, uh, ecommerce platform, video distribution platform, document processing application, community based application, warehouse management system kind of applications. Also, like, uh, I have handled around the, like, 5 members of people where I did the for them as soon as I was used to manage their task. Uh, Yeah. I think, uh, that's all from my side.

For this, uh, audio designer content to consume following best practices. Uh, in order to design the React front end, I'll have to create the React application. I'll have to set the, um, components and, uh, as well as their, uh, based on, like, the application modules, we I have to be in the different kinds of folders where I can keep my components. Uh, I will have to keep my API's request, uh, API request for request endpoints in in some environment variable. And, uh, uh, basically, just to end point, I can keep it into the environment variable and rest of the API request. I can call it using Axios package, which is a node package.

Process of integrating third party JavaScript library, helps 6 application. There are multiple ways to integrate the third party JavaScript JavaScript libraries in Relics 6 application. We can either, uh, use the chain, which is available, uh, in the for the Reliance application. We can consume it. We can add it into the chain file. Otherwise, like, we can, uh, download the JavaScript library, and we can keep it or we can use it as a a plug in into the Rails application inside the assets folder. Or we can keep it in, like, when, uh, vendor folder, basically. So, like, we can serve, uh, this kind of you can serve this kind of, uh, um, JavaScript library from the assets, which we generally maintain in the application dot JS file. So this is how, like, we can integrate the third party library using Rails application.

Approach to optimize the SQL queries. SQL queries, uh, can be optimized using multiple ways. We can use the, uh, includes, which is, uh, help us to handle the, like, uh, n plus 1, uh, issues generally happens in Reliance application. We can figure it out using. Indexing, we can add on the multiple fields. Those are frequently used for searching purpose, and those comes into the rare condition. The joints, we can perform. Um, the association should be optimized, between the database tables. Uh, another way, like, we can write it the the raw SQL queries, um, as well as, like, we can use materialized view, um, which can be quite, uh, quite good solution for handling the, like, large amount of, uh, dataset. Yeah.

Complex view template, we can handle in Rails application for the performance purpose. We can use the, uh, like, partial views, uh, at different places, and we can use the helpers in order to get the data or, uh, to like, for the reusability purpose, we can use helper, and we can consume it into the view. Uh, we can create the partial views, um, like, small small small small, uh, which can which can consume the small amount of, uh, HTML or the template kind of code inside it. And, uh, based on conditions, based on layouts, we we have to do we can able to design the different layouts for the different, uh, different kind of users. Let's take an example. There is a admin and there is a user. 2 different kinds of, uh, users, and we wanted to serve the different layout. So we can mention that the layout into the application into the controller, which we wanted to serve. And, Yeah. Such kind of things, like, we can perform to enhance the view templates.

Also testing the objects, calls, um, using MVC components, Uh, there is different kinds of way we can do that. We can automate it using Selenium in order to, like, test whether this is, uh, this next call is working perfectly. Otherwise, like, uh, if you wanted to just simply test, uh, the controller method that is working fine or not, um, when the Ajax request comes into the consideration. So we can simply, uh, test the controller using our spec. We can send the send the different kinds of parameters, uh, inside the controller method, and we can process it as per the, uh, core mentioned inside the controller's method. And by comparing the response, uh, which is coming out, uh, from the controller's method, and, uh, we can verify whether that response is correct or not. So based on these, uh, parameters, like, we can, um, test the as that's call in the Rails application.

What strategies would you employ for optimizing text full text search models application app upload across multiple AWS instances. So in this case, like, we can consume the Elasticsearch or the Solr, uh, general use for searching the full text search engine. It generally, um, perform some cache operations, maybe using that is, uh, as a option. I'm not sure exactly. Like,