Dharmik Gadhiya

My name is, and I am from Gujarat. I have a total of 4 years of experience as a data engineer, having become one at 5.1. After that, I have been working as an engineer at, for 2 years. And over the course of years, I have conducted more than 800 interviews on behalf of. So in total, I have 6 years of experience. I am an electronics engineer by background, and all the programming I have learned is from YouTube, Stack Overflow, and other various platforms. I graduated in 2016 from the DDIT, which is in Gujarat. That's all about me.

An API that requires high traffic, high availability, and high availability is very important, so I would suggest using multiple instances of a server. Against the load balancer, the servers can be hosted on different regions geographically based on where the traffic is coming from. Yep. Apart from that, I would also consider the cost. How much cost can we bear and the number of projected users, our expected load for the future, and our previous load, like, what was the growth and what will be the growth? The number of requests per second, and the number of read and write requests as well. Depending on whether there are read requests, then keep more slaves and less masters. And if the system is write-heavy, then keep more masters, it can redirect the load across various servers.

Cloud services which can be quite cost-effective, but still maintain performance. So, in order to ensure that, I would monitor the peak load for each CPU or all systems. And I will try to use as many servers as I can, but not more than that. So, basically, what I will do is try to use auto-scaling so that whenever there is high traffic, it will scale up automatically, and we can scale it down. We can also monitor CPU and frame usage, basically. And we can keep the usage at 70%. If it goes above 70%, we can spawn more instances. And as soon as the load goes below 30% or 40%, we can reduce the number of instances so that we can serve as many users as we can without bringing down any API, or breaking down any servers.

Food implementation and importance in this kind of in distributed transaction. The very easiest way to measure the item potency is just keep the last transaction in the system and update the last transaction in the database. In order to implement the item potency, basic delete plus insert queries work. First, you split all the IDs that are present for the given primary key or a combination of primary keys, and then reinsert all those values. So this will make the system idempotent. But in order to ensure idempotency in a distributed transaction system, we can segregate. We can segregate the rows based on some particular factors. If the primary keys are based on alphanumerical or alphabetic values, then we can send those rows to a specific server so that we can easily perform the delete plus insert.

What design pattern would you use to enhance the scalability of Jarvis cloud application and why? For the same pattern. So if we talk about, various Clouds. Can I guess polymorphism would be great for in, polymorphism or, Basically, interface or abstract class? So that will help us to support various cloud where is cloud vendors? Like, let's say we can support BigQuery or AWS or Azure Without, changing anything in the main code, we can just pass at the runtime, we can pass the instance of any cloud vendor or any cloud And, without changing a single code by using this interface or by using the polymorphism, we can customize it for any customer or customize our application based on the

What steps would you take to diagnose and fix a service experience and convenience failures in Kubernetes? I haven't worked that much with the cloud, but the first thing that comes to my mind is monitoring the logs and we can monitor the usage, CPU usage, or RAM usage for a given port. If it's an intermittent failure, then it's mostly due to sudden peaks or maybe a DDoS attack. If it's a DDoS attack, then we can stop those requests based on the IP address. However, this is specific to Kubernetes. I'm not sure, but I would mostly check the logs and monitor the usage. And based on the time, try to diagnose and fix.

Here's a new piece of which is using so Chris, can you identify what principle is being used and explain any issues with I don't, I don't remember the exact number. It's maybe let's go something or dependency inversion here. Basically, we have an interface, and that interface is being implemented by various shapes like circle and rectangle. However, from the core, the draw shape method that is present in the ChefFactory. When we call shape to Chrome. It seems like we don't know which instance of shape we are calling. It can be either circle or rectangle. But as far as this code goes, we don't know. If we have created an instance of ChefVictory, and if we are passing a specific shape, either rectangle or circle, then that would not cause any problem. But, as far as I can see, this seems to be the program might fail at runtime by saying that shape was not found. To fix this issue, maybe we can just rather than keeping the draw method empty in the interface, we can just give the default. We can return a default value, something like no shape was called or no shape found or something like that.

Public class StudyWord { public static void main(String[] args) { Thread = new Thread(() -> { int count = 0; for (int i = 0; i < 100000; i++) { count++; } System.out.println(count); }); thread.start(); } }

Continuous integration pipeline for a Java application I would set up would be using Jenkins or Continuous Auto-Cycle Deployment, which is also known as CICD. CircleCI is also a popular choice. Yes, if I'm unsure whether we are talking about the tool or the concept, I think it would be helpful to take an inside view. Or we can see if there's anything available on GitHub that we can use. But, yes, we can also use GitHub if there's something that can be used.

Start to see this. You might have to go from one cloud provider to one without service encryption. Yeah. Yeah. Again, here, we can take our use of an interface or polymorphism. And we can even start supporting one vendor or one cloud provider. We can pass it via an interface. And once we have implemented it, we can just switch to another cloud provider. So this is a migration and API from one cloud provider to yeah. I guess we can use that. Try to use polymorphism or an interface, which will be easier to implement, and it will help us.

To ensure consistency of data in distributed databases when handling cross-region transactions, maybe we can use locking the table when updating the data, which is okay. We want to keep the data consistent with distributed data. One easiest way that I can think of is to do an atomic update. If there are different databases for each region, then just update the data to all the databases.

How would you incorporate machine learning models for child is Microsoft architecture? I don't have any experience with the machine learning. so, yeah, I will skip the question.