 Hello guys welcome back to our channel, so today in this video we will be sharing the entire equations for experience part 2, so if you haven't followed the part 1, I would suggest you to go and follow the part 1 because in the part 1 also there are very good equations that we have already shared and this video is contributed by one of our friend, subscriber friend, his name is Santosh, so let's quickly get into the equation that we have shared. So first thing, so first section I would say, so we have divided into sections, so first thing the questions were on functional interface, why functional interfaces, can functional interfaces have default and static methods, yes we can have, why functional interface has only one method because it works with lambda expression and there are multiple expressions, multiple method, lambda's expression won't work on that, that is the reason we have only one method, so these are the three questions about functional interfaces. So the next section is of scope of lambda, so basically lambda doesn't have any, its own scope, so whatever scope it is getting enclosed, the same scope it will be having, so if at all, if you are declaring a variable, same name variable, instead of lambda scope which is present in outset scope, so at that time we will be getting an exception. On Apache Kafka, like explain about Kafka implementation in Springboard, can I use Kafka without zookeeper, so honestly we cannot use Kafka without zookeeper, we need zookeeper on top of it, Kafka was and we, you need to, like comment Kafka configuration, you need to explain about everything, like what all dependencies you have, what all classes you need to configure, like producer, consumer classes there are, so we have to talk about everything. Coming to the next section, what about acid property in microservices, like transaction, when the transaction is scaling about multiple microservices, like how do you handle, like how do you guarantee the acid properties in microservices and your transactions are scaling across services, so in that scenario, you have to explain like how, like how would you handle, so it varies upon from project to project, it's completely depending upon your project, you can answer this question. So next on REST APS, put versus patch, we have to explain the list down the differences between put versus patch or in machine address we use, put and in machine address we go to patch, how will you implement put rest doc, say put can also save data when the data is not found, so it's simple, basically ideally put was for that, so whenever the data is not found, we need to have a method like update or create, if it is not found, we will directly create, if it is found then we will update the properties of the entity and we'll save that, have you implemented delete mapping? Yes, of course, depending upon your project, if there is a scenario of deletion of entities, then we have to design delete mapping, delete not a frequent implementation of products, explain why, so basically I am also not sure on this, like why it is not frequent implementation or we can, maybe the scenario would be like soft delete, the interviewer might be asking about the soft delete, basically in the soft delete, we don't explicitly delete the record, but we will inactivate the records in the DB, so these are the questions on REST API, next about bean configuration, two beans are there in my config, I want bean be should get initialized before bean a, how to achieve it, so basically if you have in spring good, we have a annotation called a Dread Conditional Annotation, there we can mention like on which bean gets depends, so using that Dread Conditional Annotation depends, we can achieve that, so two configs a and b in spring mode, how to use config means inside config, it is simple only, first is stick locking versus optimistic locking, so basically optimistic locking is when you check if the recall was updated by someone else before you come in the transaction and come into persistent stick locking is when you take an exclusive lock so that no one else can start modifying the record, so this is about these two different types of locking, transaction management, so the question might be like what is spring, how we can do transaction management in spring there are two ways, programmatic way and declarative way and what happens under the Dread Transactional, so I have to explain how the transactional, Dread Transactional Annotation works inside, I have some code inside static block and some code inside is Dread Post Construct block, which will run first obviously static will run first then the code that is written in the post construct will run. Next question can explain OAuth 2 process, so I have to explain in detail about the OAuth 2 process, if you are not aware of it, you have to, like if at all you have used it then this question would come up, but all your project itself is not having, we are not using OAuth 2 process when no one would ask you, but if you are implementing it, you have to know each and everything, especially when you are an experienced candidate. Different API gateways why need them, so API gateways basically intercepts all the incoming requests and sends them to the API management system, which handles a variety of necessary functions, some common functions include authentication, routing, rate limiting, billing, monitoring, analytics, security, there are many things that can be done true in the API gateways, so here are the, we can set up four, like con gateway, Amazon API gateway, TYK gateway and Kraken D, so in our application we use Amazon API gateway, design patterns, so next section is design patterns, what architecture design patterns to use with containers, and the first question, every question comes through a series of checks, basically multiple if loops, like more than four to five, and these have some concrete implementations, what pattern suits this scenario, which feature in cloud do you think is best according to you and why, so these were the questions that were asked on the design pattern, so it varies again from project to project, microservices is the next section, so these were the questions that were asked as part of microservices, how will you decide if you are ready for adapting microservices architecture, monolithic SOA and microservices, basically difference between a monolithic application, SOA, architecture application and microservice architecture application, how to decompose a monolithic project, so this is the biggest challenge any developer will ever face, converting a monolithic application into a microservice application, disadvantages of microservices is there are few disadvantages, maintaining them is a big problematic and it is what I can say cost effective in terms of cost also it is, in terms of cost also we need to spend few extra dollars compared to monolithic and SOA type of application, how will you implementation communication between microservices, so we can use Saga pattern, so in my application we use Saga, so right now that is the thing that is the second moment, there is one more thing, a two-phase commit is also there, logging mechanism for microservices, sorry logging mechanism for microservices, so there are a lot of ways to my log, so it depends again upon from project to project which design best suits you, YEL test I can stop slung for logging, honestly I have no answer for this, so as far as you know both are very good, deployment of microservices, so how they get deployed, who is going to decide the cluster number of applications of all things you need to talk, mostly if I am not wrong DevOps teams will take care of this thing, importance of Springboard profile gives you scenarios where you use it, so basically Springboard profiling is very important thing like because there are scenarios where in the lower environments we may not be using few functions like functionality of like especially if you take auditing we don't want that to be logged in local or testing environments but in production we want that so in that scenario based on profile we can load auditing beans and we can audit the things whatever we want, caching mechanism like how we have implemented might be the question, do you think we can use a database for caching, so there are applications that use databases for caching, so yes we can use but again this depends upon where is from project to project, explain how deletion works honestly no answer, I don't know the answer I haven't worked in that, so these were the questions that were shared and here is the main that we have received, this we have received on 11 November 2021, so sorry my friend unfortunately we have taken a lot of time to put into video because most of us have busy in their personal life and professional life so we are not getting the time, so you can go to the questions that we have shared there were close to 34 questions that we have discussed I hope this video helps you and thank you for watching if you haven't subscribed please do subscribe and share this video and if you want to contribute to our channel you are most welcome you can send out the email to or give an email id in the description and thanks for watching