Java Spring Boot 3 Yrs Interview Experience

Hinzugefügt: 2026-05-06

[00:00:00]Hey guys, today we have a fun and he's having total three years of experience in Java Spring Boot and microservices.

[00:00:06]And guys, those who want to give same framework interview, please fill out the form below in the description. So, now let's get started. Yeah, hello fun. How are you?

[00:00:14]Hi Faizan, I'm fine. How about you? Yes, I'm also good. Shall we start?

[00:00:19]Yes, yes Faizan. Okay, so Afan, can you please introduce yourself and your recent project in brief?

[00:00:24]Yeah, I'm Sheikh Afan as a Java developer. I have an experience of 3 years in designing developing software solution. I specialize in core Java, Spring Boot, Hibernate, restful APIs services. My recent project was one of the leading company. I have been deployed to the one of the high profile client where I have been work with a station development management system for the project. So, prior to this, I also have an experience with the other company which I have been square shipping project, booking and tracking management module where I have been done with the truck model. This is my simple introduction. So, since I have been work with the client, I have been experience with the live bug fixings and This is my simple introduction. Okay, got it.

[00:01:09]Okay, so Afan, uh I think you are using Java 8 version in your project or maybe Java 8 plus 11 17, right? So, I just want to know one thing. Uh in after Java 8, we have default method, private method, static methods in interfaces.

[00:01:27]All right? So, I just want to I just want to know the reason behind it.

[00:01:31]Uh in the Java 8, default method, private method, static method was introduced due to in the in the interface, we have only the public static and we have only the method which is which do not have an implementation at that time. Mhm. So, due to that constant of the it do not have an implementation with the child class, then default method was been introduced in the Java 8. Okay.

[00:01:54]>> To make our custom logic.

[00:01:56]Okay, so Afan, if a class if a class implements two interfaces that both have a default method with the same signature, Okay. so, what will happen?

[00:02:10]It will get the ambiguity issues.

[00:02:13]Correct.

[00:02:13]>> With the two different It will give compilation error.

[00:02:16]Compilation >> The class must explicitly override the conflicting method, right?

[00:02:21]Yes. Okay, Afan, can you tell me can a abstract sorry, can an abstract class have a constructor?

[00:02:30]An abstract class don't have an do not create any object. Mhm.

[00:02:36]>> So, in my understanding, it doesn't have any constructor in it. We have only abstract methods on it.

[00:02:42]Okay. Uh but the answer is yes, abstract classes can have constructors. But we cannot instantiate them directly.

[00:02:50]By a new abstract class is uh it's basically a compilation error.

[00:02:55]>> object of that abstract class. The constructor may be called via super method.

[00:03:00]Yes, yes.

[00:03:01]>> From the concrete sub class, okay?

[00:03:03]Yes.

[00:03:04]Okay, got it.

[00:03:06]So, just tell me one thing. Uh why does integer I N T E G E R is equal to is equal to integer work for a small numbers but fail for larger ones?

[00:03:20]You got it?

[00:03:22]Yeah, due to uh It is integer is a wrapper classes.

[00:03:26]Okay, I'm saying let's say there are two integers integer A is integer B.

[00:03:32]Okay, so if we do A is equal to is equal to B, this will work uh for small numbers, but for large numbers, this will not work because let's say if we have A is equal to 1,000, B is equal to 1,000 and if we do A is equal to is equal to B, then it may return false.

[00:03:49]Because integer is considered an object, right?

[00:03:54]Integer is an object, yes. So, why it works for small numbers?

[00:04:00]I if it was small numbers in terms of primitive data types or the just numbers Okay. Let me give you an example. If you have integer A is equal to 10 and integer B is equal to 10. So, okay?

[00:04:14]When we'll do if A is equal to is equal to B, this will always return true.

[00:04:18]>> Okay, but if we A is equal to 1,000 and B is equal to 1,000.

[00:04:23]Right? This will not give you a true result. It will occupy the different memory locations.

[00:04:30]Okay. Okay.

[00:04:32]Let me tell you the answer. Actually, Java caches integer objects for values minus 128 to 127. You can miss >> Okay, so if you compare the values between minus 28 to 127, double equal works perfectly.

[00:04:46]It will not treat these numbers a different object a different location.

[00:04:50]But beyond 127, yes, you may see some incorrect inconsistent result, okay?

[00:04:56]Okay, okay.

[00:04:58]Okay. I would like to share one important thing with you. Actually, we had launched complete interview preparation material is structured step by step by myself expert in MNCs interviews. And the best part is that now no one need to go anywhere else to prepare the interviews, okay? There is a 99% chance that interviewers will ask questions from this material. So, basically, it contain a lot of material categorized by experience level means each experience level has different material with all possible interview question and answers for Java, Spring Framework, Maven, Git, Spring Boot, Spring Security, Spring Data JPA, Kafka, microservices, Java coding questions, stream API coding questions and many more. I have provided the link to get this in the below description. And if someone need this material, whole material plus two real enterprise client projects for the reference plus one-on-one lifetime doubt sessions and the referrals to the big MNCs, then they should check the interview preparation kit. I'll provide the link for this as well in the description below. So, now moving to our interview. Um can you explain what is method overloading and what is method overriding? And which is resolved at compile time and run time?

[00:06:04]Uh method overloading is a same method name having in the same method name having with the different parameter, sequence of parameter, types of parameter would be changed in the method overloading. It is a compile time polymorphism. Method overriding is a run time polymorphism where method name would be the same but different parameter return type would be the different and sequence would be the different. This is a run time polymorphism.

[00:06:28]Got it.

[00:06:29]Can we achieve polymorphism without inheritance in Java?

[00:06:35]Without inheritance, yes, we can achieve the polymorphism without inheritance.

[00:06:40]Correct, we can achieve. Afan, can you tell me what's the difference between array list and linked list and when would you choose one over another?

[00:06:49]Yeah, array list and linked list was a implementation of the list. In the array list, we have the index position. When we want to fetch the any data of the position, then we go with the array list. Linked list, it is internally work with the node representation. Okay. Uh doubly linked list, it it was internally work with the doubly linked list where we have a node representation. So, it would be the slow in the link in the in terms of linked list. Mhm.

[00:07:15]Okay.

[00:07:16]>> So, Okay, so you need to iterate over a list and removing matching elements.

[00:07:22]What's a wrong way to implement it and what's a right way to implement it?

[00:07:27]Uh sorry, could you please repeat it?

[00:07:29]You need to iterate over a list and removing matching elements. Let's say you have a list 1 2 3 4 5 6 7 8 9 10 and you have an matching element for example 8 and you have to iterate a list and remove that matching element from the list.

[00:07:43]So, what's a right way to do it?

[00:07:48]Iterator dot Like would you use list array list?

[00:07:52]Would you use linked list? Oh, sorry.

[00:07:54]Um yes, linked list. Like what which which collection would you use and how would you use?

[00:08:00]We go with the array list to iterate over the list list dot Okay.

[00:08:05]>> We want to fetch the Yep, yep, yep. First, we will we will go through I mean, we'll use the array list or linked list, right? Uh but you will see concurrent modification exception because you are removing something while iterating.

[00:08:19]>> we remove concurrent modification exception we use. We deal with the iterator dot remove method to prevent that concurrent modification exception while threads are accessing a uh while threads are accessing in the iterator, it will get the exception.

[00:08:35]Correct, correct, correct. Okay.

[00:08:38]Um so, uh let's say you want to store some integer values, okay?

[00:08:45]In a pair.

[00:08:46]Okay?

[00:08:48]But uh you don't want to store the duplicates one.

[00:08:52]Right?

[00:08:54]But you have to maintain the order. So, which uh collection framework would you use?

[00:09:01]Duplicate order should be maintained but uh There should be no duplicate elements.

[00:09:06]You have to store the value as a key and value. There should be no uh duplicate keys, but the insertion order should be maintained.

[00:09:16]Okay, insertion we go with the hash set.

[00:09:20]Hash set? Are you sure? Uh Yeah, yeah.

[00:09:23]Do we maintain the insertion order in a hash set or hash map?

[00:09:29]In my head, yeah, hash map is a answer we do which maintain the orders.

[00:09:34]Uh no, no, no. My question is uh let's say you have a stored the element in the hash map or hash set.

[00:09:41]Uh do we I mean, hash set maintains insertion order?

[00:09:46]For example, if you if you have inserted first one, then two, then three, then four, then five. So, does hash map provide guarantee that if If have inserted one first, then one should come first. If you have inserted two at the second time, then two should be there.

[00:10:01]>> No, priority of order doesn't maintain in the hash. Doesn't maintain the hash map. So, I think we should use a different collection, and linked hash map, if you know.

[00:10:11]Linked hash map maintains insertion order, right?

[00:10:14]Yes. Yep, yep. So, in this case, we should use linked hash map.

[00:10:20]Okay, so can you tell me what are lambda expressions and functional interfaces?

[00:10:26]Uh lambda expression one of the feature of the Java 8, where it was being written for the concise and the crispy to make the code. So, in the functional interface, suppose we have an a written in the interface with a some method. We if we haven't taken a method, to use the to use that method, we use the lambda expression by >> [clears throat] >> lambda expression to call that particular uh particular method.

[00:10:48]Okay.

[00:10:50]So, in the lambda expression, we don't have any return type.

[00:10:54]Okay. And there should be one um abstract method, right? In the functional interface.

[00:11:00]>> abstract method in the interface.

[00:11:02]Okay, let's say uh there is an interface, normal interface, that has one abstract method.

[00:11:09]All right? Now, there is another functional interface.

[00:11:13]Now, functional interface is implementing the normal interface.

[00:11:19]And inside the functional interface, you have uh implemented one abstract method, because if you know uh like in functional interfaces, there must have one abstract method, right?

[00:11:29]Is it possible?

[00:11:34]As we have two interfaces, we have two abstract methods, right?

[00:11:37]Mhm.

[00:11:38]Uh First is interface A.

[00:11:42]Interface A has one abstract method.

[00:11:44]Second is functional interface B.

[00:11:47]Implements A.

[00:11:49]Now, inside functional interface B, you have one abstract method again.

[00:11:53]Is this Is it possible?

[00:11:57]Uh to implement the interface to implement the abstract method. Yep, yep.

[00:12:03]Yeah, we can implement it by using the super.

[00:12:05]Uh we need to choose which method we need to implement. Okay. Uh I think you didn't get my point. Uh There There are rules in functional interfaces. We cannot have more than one abstract method, right?

[00:12:19]>> One abstract method, single abstract method we can do.

[00:12:20]>> We have already one abstract method inside functional interface. If we implement another interface that has one more abstract method, then in total, we will have two abstract method.

[00:12:31]In our child interface.

[00:12:33]Yes, but there are the two interfaces we are dealing with it. First interface and second interface are two different interfaces.

[00:12:38]>> They are two different interfaces, but if we have implemented first one, then in the second one, all the properties, I mean second will acquire all the properties of first one as well, right?

[00:12:49]Yes, yes. It will be breaking It will break the rules, right? So, there there will be some compilation or run time errors, right?

[00:12:59]Okay. Um moving ahead.

[00:13:03]Can you tell me how stream API works? Do you know Have you worked with the stream API?

[00:13:09]Yes, I don't work with the stream API.

[00:13:12]Okay, okay. Please go ahead.

[00:13:15]Uh stream API is a collection of objects, where we have the methods as filter, sort, and the map Okay.

[00:13:22]the collection of objects. As an example, uh if you want to have the stations, some of the list of the stations we have, Mhm.

[00:13:29]>> to get the in the order to get the only with the specific we need to start with the particular element with the start with the C, start with the J. Which station we are picking up. So, in that we apply with the stream filter, map in the map filter, and in the filter, we use the start with method, and we write that uh element. Correct, correct.

[00:13:51]What's the difference between map and flat map?

[00:13:55]The map is a one-to-one mapping. Map is for one-to-one mapping. Flat map is also one-to-many mapping.

[00:14:01]One is not for the nested structure. Uh one is for the nested structure in the flat map.

[00:14:07]Okay.

[00:14:08]>> So, in the map, we use in the in example in we have used the DTO to entity and entity entity to DTO to map. We use the map method in it. In our project, we use it. And the flat map we use for the nested structure as a support we have in a project that every project has the particular employees. So, for every project has particular employees, we get into the in a single single stream. So, then we use the flat map.

[00:14:36]Mhm, got it.

[00:14:37]Uh what's the difference between a process and a thread?

[00:14:43]Uh thread is a small unit of a program, where process is a uh uh where pro Thread is a small unit of program, and where pro process is a uh it is a part of the thread, multiple uh what we call Okay.

[00:15:03]A process is basically an independent program with its own memory space, file handles, and operating resource, isolated from other processes.

[00:15:12]Thread is a lightweight unit of execution within a process.

[00:15:16]Within the process.

[00:15:17]Uh in the project, context switching will be the difficult, and a thread is a very easy to context switching. So, process is a very expensive, and a thread is very lightweight. Correct, correct.

[00:15:28]How can we create a thread in Java?

[00:15:31]Uh we can create the thread in a Java by the two ways. One is a runnable interface, one is the extend with a thread. In the when we call the runnable interface, we have the implementation of the run method. We use to perform the task on it to execute that particular task.

[00:15:46]Okay, got it.

[00:15:48]Uh what is a race condition?

[00:15:51]If multiple threads are accessing with the same multiple threads accessing the same resources, then we used to get the as race we used to get the data as a race condition, which makes the data as leak or corrupted. Okay.

[00:16:06]Got it.

[00:16:08]So, can you please tell me um how synchronized keyword works actually?

[00:16:19]Uh suppose there are the two threads if are accessing with the same resources.

[00:16:23]One thread is going to access in the uh resource one, and second thread is accessing for the resource two. But resource one is depending on the resource two, and resource two is depending on the resource one. There is a lock uh there would be the lock. Nothing would be released from the resource one to resource two. Then we use the synchronizer at the method level or the block level to prevent this uh race uh race conditions.

[00:16:46]Okay, got it. Can you tell me what is executor service, and why should we use it instead of creating threads directly?

[00:16:54]Uh I have not been worked with the executor service, but in conceptually, I know the executor service we use the executor service framework, where we use the multi uh where we multiple threads put into one place, and we give the every thread as a task to perform.

[00:17:11]Okay.

[00:17:12]Do you know about future?

[00:17:15]No, I don't know.

[00:17:16]I don't know.

[00:17:16]>> Completable future?

[00:17:19]No, no idea about the future.

[00:17:20]>> idea.

[00:17:21]Uh can you tell me what is dependency injection, and how does Spring implement it?

[00:17:28]Uh dependency injection is a technique where we use in the in the Spring Boot, and we have the three types of dependency injection. One is the field injection, constructor injection, and the setter injection. So, in the field injection, suppose in the we have in a controller, we use we are we are making the dependency as service in that controller to get that business logic. Okay.

[00:17:49]>> Or repository to get some operations of it. Then we use the at the rate auto to just private uh station service station service in the station controller. So, through this way, we use the field injection. In the setter injection or constructor in in the constructor injection, with the mandatory to work with it. In the setter injection, we don't we don't want to There is no mandatory on it. Mhm, mhm.

[00:18:14]We use the at the rate auto wired for the dependency injection to work.

[00:18:19]Got it, got it.

[00:18:20]Um Why is field injection considered a bad practice compared to constructor injection?

[00:18:30]In the field injection, we cannot the we cannot test we cannot test in the field injection. Mhm. Uh so, we don't use the much in the field injection. Constructor injection, suppose we have an account class and the transaction. Without the transaction, we could not perform the any accounts. So, it is mandatory to there in the constructor.

[00:18:50]Okay.

[00:18:52]So, that we use the mainly constructor injection.

[00:18:55]Got it.

[00:18:55]>> usually used for the testing purpose also.

[00:18:58]Okay.

[00:18:59]What's the difference between component, service, repository annotation? And can we use the service on repository and repository annotation on service files?

[00:19:13]A component is a Sorry, component?

[00:19:18]Okay, forget about component. Just tell me the difference between service and repository annotation, and also tell me whether can we use service annotation on repository files and repository annotations on service files.

[00:19:29]Yes, we can both in the service annotation we use with the at the rate service at the rate service annotation, which is a stereotype annotation.

[00:19:37]Component, service, and the repository all are the stereotype annotation. In the service in the service class, we work with the at the rate service, and in the to use for the business logic, we use that service class. And the repository we we work with the database operations.

[00:19:57]With the with annotation of the repository which extends the JPA which perform the database operations in the application.

[00:20:04]>> [clears throat] >> Okay.

[00:20:06]Got it. Can you tell me what is Spring application context and how it is different from bean factory?

[00:20:13]Uh If I'm not exactly recalling with the bean factory which is old the application as I'm recalling that we can get the whatever the bean required we we can we can get that as an application context CTX is equal to new annotation configuration application context with the CTX we get with the get bean method we give the bean method of it with the return type.

[00:20:37]We fetch what beans we required in them.

[00:20:40]Yep, yep, yep. Actually, bean factory is a basic Spring IOC container, lazy initializes beans on first request, minimal footprint. Whereas application context extends bean factory and adds eager singleton initialization and startup, event publishing, and a lot of things like AOP integration, resource loading, etc. Okay?

[00:21:01]Okay, so Afan, can you please tell me the difference between request param annotation and path variable annotation?

[00:21:10]Yeah, in the path variable annotation we go with the specific with the specific thing we go with the path variable ID. As example, we with the stations we are searching with station search station station ID.

[00:21:24]Okay.

[00:21:26]With the method name we used to provide we used to provide it. Station ID in the request param we fetch the data from the query params which give the dynamics value.

[00:21:39]Basically, these two differences we have request param and the path param. Got it. How does a Spring validates a request body object?

[00:21:49]What annotation would you use?

[00:21:53]Sorry.

[00:21:54]Okay, so let's say you have created one API and you have mentioned at the rate request body annotation there just to get the request body, right?

[00:22:04]Now, you want to validate the fields of those request body.

[00:22:09]>> Yep, yep.

[00:22:10]>> At the rate valid we use we use as request whether it is a right request or wrong request. If it was right request, the process will go forward and if it won't then it will the not process the request further.

[00:22:24]Okay.

[00:22:25]And what are the validations annotations at field level?

[00:22:32]At the field level we use the at the rate not null, not blank, at the rate size, positive, at the rate negative.

[00:22:41]These are the field level annotations we use.

[00:22:45]Okay, got it.

[00:22:47]Um can you tell me um what is controller advice annotation and how do you use it for global exception?

[00:22:58]In the global exception we used to handle the centralized all the exception at one place. We use the at the rate rest controller advice at the rate rest controller advice.

[00:23:07]We create the custom exceptions first and we handle in the at the rate rest controller with the proper error responses. We set the data and the fields to get the response clearly to the client.

[00:23:21]Got it.

[00:23:23]Okay, moving ahead to um Can you tell me what is the difference between eager and lazy fetching in JPA?

[00:23:34]And what are the defaults in our Spring data JPA?

[00:23:39]Uh Spring in the Spring Boot by default it is a eager loading when it was coming to the loading. Uh suppose in the lazy loading we we are getting from the uh child entities along with the parent entities.

[00:23:53]Parent entity as an example when user is calling with the orders order it getting along with that particular order ID. So, we used to manage the at the rate fetch type dot lazy or fetch type dot eager.

[00:24:06]Okay, got it.

[00:24:08]Um moving ahead, what is lazy initialization exception error?

[00:24:16]Lazy initialization exception I'm not able to recall it now.

[00:24:21]>> Okay. So, basically when no session occurs when you try to access a lazy loaded relationship after the JPA session has been closed.

[00:24:30]Okay.

[00:24:32]Okay, can you tell me the difference between save method and save and flush method?

[00:24:39]Yes, both are the database operations in the while while if while the user is saving particular thing it directly directly directly don't change in the save method. Okay. In the save save and flush method whenever a user is changing something it instantly changes in the save save and flush but it degrade the performance in the save and flush.

[00:25:05]Okay.

[00:25:07]Got it.

[00:25:10]Okay, so let's say you catch a generic exception in your code and log it.

[00:25:16]Okay.

[00:25:17]Okay, so I mean you just want to catch a generic exception and want to log it. So, how would you do it?

[00:25:28]Generic exception as an example >> Through your REST API, let's say you want to catch a generic exception.

[00:25:35]For example, runtime exception, null pointer, class cast, interrupted exceptions, these.

[00:25:42]So, how would you do it?

[00:25:44]We used to directly handle with the try and catch blocks inside the controllers.

[00:25:49]Okay.

[00:25:52]Yep, and also we could use the global exceptions, right? Global exception handling we mostly use with the global exception handling. Or we specific specific exceptions we create with the general exceptions and we used to present them.

[00:26:05]Correct, correct.

[00:26:06]Okay.

[00:26:08]Um Do you know about singleton design pattern and what are the common issues with it and how would you implement it safely?

[00:26:17]Yes, we have used in the singleton design pattern in our application. It is only one instance created for the container. Okay.

[00:26:25]Okay. As an example, we have an in our project we have used the configuration with the railway config which used it to load the preload before starting the application zones, divisions, and the stations and we use that in the services by using the at the rate auto wide dependency injection so that we can use we can use in the services wherever we required.

[00:26:45]Yep, yep. Okay.

[00:26:48]Um How would you write a JUnit test case that a class depends on a singleton?

[00:26:59]We have been not written any test cases here with the JUnit but we have been with the postman we have we have in a front end in the Angular.

[00:27:08]We directly test with the Angular at that time.

[00:27:11]Okay, so basically singleton make testing hard because you can't inject a mock.

[00:27:17]The class reaches out directly, you know?

[00:27:20]Yes, yes.

[00:27:22]Okay.

[00:27:23]And do you have any experience with builder pattern?

[00:27:28]Yeah, I do have an experience with the builder pattern.

[00:27:32]Please go ahead.

[00:27:34]Whenever we are creating with the complex complex objects then we use the builder [clears throat] design pattern. As an example, we have the constructor overloaded so constructor overloaded in our project so that every time we are creating the different different objects for it. So, we used the custom custom builder pattern by using the at the rate builder.

[00:27:59]At the rate builder we used to set at the rate builder for it.

[00:28:03]Got it.

[00:28:05]Uh Okay.

[00:28:08]Moving ahead, can you tell me how does the open close principle apply to payment system that keeps adding new payment methods?

[00:28:18]Uh I have not worked with the solid I have not prepared for the solid means Okay, you don't know the solid principles?

[00:28:25]Yeah, I do know I do know the basics but I am not particularly in that uh Okay, okay.

[00:28:30]Yeah, it's fine. Do you know open close principle?

[00:28:34]Yeah, I already but I have not been uh in that >> Got it, got it. Are you using Git commands?

[00:28:42]Yeah, we are using. Of which Git commands do you use most of the time?

[00:28:47]Most of the time we use the Git commit, push, pull, stash for the temporary storage.

[00:28:52]How do you resolve Git conflicts?

[00:28:55]Whenever committing the same file with the two other developers then we get the Git conflict.

[00:29:02]So, we used to edit there and see the code which the is appropriate code and we used to remove and we commit it.

[00:29:10]Okay.

[00:29:12]Have you used Git cherry pick?

[00:29:15]Sorry. Git cherry pick.

[00:29:17]No, I have not used. Okay. Have you used Git rebase?

[00:29:26]No, I have not used. No, okay. Which one you are using for building project, Maven or Gradle?

[00:29:33]We are using the Maven. Maven. What's the difference between Maven clean and Maven install?

[00:29:39]Maven clean we use the for the cleaning the repositories cleaning the project which we are the injecting the dependencies in the class class path.

[00:29:49]And uh Maven Install.

[00:29:53]Uh Maven installing the reinstalling the packages whatever we are included in the dependencies in.

[00:29:59]Okay. So, let's say you want to create a REST APIs, a simple CRUD application for I mean and you have to include the REST API.

[00:30:09]So, what dependencies would you use in your palm?

[00:30:13]Or add?

[00:30:15]>> Uh we use the starter dependencies with the Spring Data JPA. Mhm. Uh which bring the dependencies of the Spring Data JPA we use it and uh Lombok annotation we use and for the other data no arc constructor all the data all all arc constructor for the Lombok annotations. Mhm. And uh we use the Yeah, data JPA Lombok annotations and uh my we use the MySQL So, why do we use Lombok?

[00:30:47]We use the Lombok annotation for the no need to write the all times every time with the getter and the setter methods to reduce the boiler plate code.

[00:30:56]Okay. So, uh do you know the servers that we have in our Spring Boot application?

[00:31:01]Server? Servers.

[00:31:05]Yeah, we have used the Tomcat servers.

[00:31:08]Okay. So, what's the purpose of servers for our application? What Tomcat do?

[00:31:15]We deploy the application for the deployment purpose we use the Tomcat.

[00:31:20]Okay. Have you used Jetty?

[00:31:23]No, we have not used any Jetty. Can we use in the future?

[00:31:27]Yeah, maybe we use the in the future.

[00:31:29]But uh How can we use? Like what would you do in order to use Jetty?

[00:31:34]Uh I don't uh have the idea about the Jetty. We use the Tomcat mostly. Okay.

[00:31:40]>> for the deployment of the What's the default port number?

[00:31:44]8080 uh sorry, 8080.

[00:31:46]>> want to change it to the different one?

[00:31:49]Uh we used to present our application.properties we used to give the our custom number as 89090. So, which one do you like most application.properties or application.yml?

[00:32:01]Uh we have used in our project application.properties, but application.yml is rightly we are using in the industries which is a indentation Okay. So, let's say if you have two files application.properties and application.yml, our application will pick which one?

[00:32:21]The configuration I have not encountered this issue. Okay. Okay.

[00:32:25]Got it. Have you encountered a circular dependency issue?

[00:32:32]Yes, I have encountered the circular dependency issues. Okay. What was that?

[00:32:36]>> is injecting into the another dependency. And how did you resolve that?

[00:32:41]Uh by using the lazy annotation we have we use the lazy annotation. Correct.

[00:32:45]Correct.

[00:32:46]Okay. So, uh Shake, it's done for my end and yes, it was a very very nice interview.