INFOSYS | real time java interview series| Interview 21 | java interview buddy

If you want to give a mock interview for the preparation. please follow the below steps.

step 1: Like this video
step 2: subscribe to the channel
step 3: message me following thing to my instagram id.(java_interview_buddy)
I will reply with an available time slot.

my instagram id: java_interview_buddy

Name:
Technologies:
Years of experience:

If you want to buy me a coffee :

mock interview

java mock interview

Tech Mahindra Interview

java interview questions and answers

java interview questions and answers for experienced

telephonic interview for java developer

java telephonic interview

java telephonic interview questions for 3 years experience

java telephonic interview questions for 5 years experience

spring boot interview questions

spring boot interview questions and answers for experienced

java interview questions and answers for freshers

microservices interview questions
core java interview questions and answers

java 8 interview questions and answers

accenture interview experience

infosys interview for freshers

java developer interview questions and answers for experienced

spring interview questions

spring boot interview questions, spring boot interview questions and answers for experienced , spring boot interview questions and answers , spring boot interview questions code decode , spring interview questions , spring boot interview questions and answers for freshers,spring boot interview questions for experienced,spring boot,java spring boot interview questions and answers,spring boot interview questions for experience,top spring boot interview questions,java interview questions and answers,java interview questions,java 8 interview questions,core java interview questions,spring interview questions and answers for experienced,tricky spring boot interview questions,best spring boot interview questions,commonly asked spring boot interview questions,java,spring mvc interview questions,spring boot interview questions & answers,spring boot tricky interview questions,java programming questions,spring boot microservices,code decode,spring boot security interview questions,spring boot actuator,interview questions and answer spring boot

[sahilkhanna]

Hey Sharing little stuff hopefully helps. But I'm sitting just normally and writing But in interview more pressure. Please give me Mock interview chance I'm not on Instagram.

Edit: Added Last Question I missed that one.

1. Difference Between Stack Memory & Heap Memory.
Ans: Stack Memory is fast Heap Memory is slow. (Object stored in stack but String literals are store in Heap like Ram String literal from pool used many of the objects). Not having more Idea on this.


2. TreeSet => TreeSet is Subset of Set interface as we know set interface helps to remove duplication same TreeSet doing But tree set gave us the final data in ascending order.


3. ApplicationContext => It is like the MetaData of the whole application which helps to do many thing like getting environment properties getting beans. (One Ex of other tech like in Flutter BuildContext Plays an important role).


4. Profiles => Able to set profile in different ways one common way to declare property inside application.properties file (spring.profiles.active=dev), For usage case if we want to enable any Bean at dev only then Ex:

@Service
@Profile("dev")
class devBin{}


5. Benefit of Creating Bean => Helps to do the things Loose Cupled way, no need to create new object again and again just one object is used with in the whole lifecycle.


6. Actuator:- Helps to do Health check and most stuff. But one recent I used with my MS helps to refresh the application properties by hitting it's refresh url there are many for such of use case for use it's matrics for charts and all that stuff for analysis.


7. Disable Auto Configure:- I never tried this yet But if you want any properties that should not be configure or beans should not be created then we are excluding that class like


8. MicroServices (MS):- Helps to breakdown the application in small applications. I think the phrase mostly used that if one MS is down then any other will not affected, Because we have to design the microservices in that pattern so that all other will not go down. It's all depend on configured pattern.


9. *Deploying MS*:- So we know one App has many MS's so to deploy each manually it's headache we need to use CI/CD for this purpose different CI/CD way like using AWS CI/CD Pipeline or Jenkins.


10. *Routing In MS*:- We are using service Discovery for this purpose because it's lot difficult if we change any MS port then we have to change with in other MS so service discovery makes things easy. Popular Service Discovery Like: Eureka, Spring cloud consule.


11. *Reactive Java:- I didn't use yet so no Idea.*


12. Security in MS:- For me I'm using Custom Resource Server and Authorization Server for this purpose. and also other Pre-Built Authorization Server like Github, google etc.


13. *Docker with Java:- Never tried with Java yet But having Idea to use with Django.*


14. More Load in MS:- We will do Load Balancing (One app with multiple instances) using netflix-ribbon or if we are using Eureka then there is inside netflix-ribbon dependency available no need to add explicitly.


15. *Patch vs Put:- Put helps to modify the existing data but with Patch we are doing small changes or to know which url availables (Do google pls not more knowledge) . POST helps to post or add new data.*


16. Custom Methods:- We are able to use inside Repository using Query Annotation and also we are able to use on the Entity Class itself able to write JPQL query inside query annotation for update also need of @Transactional.


17. Java 8 new Features:- Mostly which I used is Streams (Great stuff for processing data with minimal code) and Lambdas (not using more).


18. Disadvantage of Lambda:- Till now I didn't faced disadvantage. But I think there is a problem of throwing Exception inside Lamdas because we are doing processing internally not sure Sorry.


19. Stream Methods Like: filter, map, sorted, foreach etc.


20. Date Time API:- Using more for storing and sending formatted date and also for doing date after or before type things.


21. *Design Pattern: Not much Idea may be I used anywhere but I will try to visit this for knowing what is actually this.*


22. Stream Different From Collections: Streams are basically more used for processing the data and send back the final data but in collections it helps to store the data in different data structures. Yes Streams are lazy and Non-Resuable once the flow is gone from the stream once it can't be execute again you will get Error:- Operation already executed.


23. YAM vs Properties File:- Major diff b/w yaml and properties yaml removes duplicacy whether in properties file every property need to be writted fully.


Thanks a lot for reading.