Explore topic-wise InterviewSolutions in .

STRATEGY deals only with DECISION MAKING at runtime so INTERFACES should be used.

Strategy deals only with decision making at runtime so Interfaces should be used.

Factory is a creational design PATTERN whereas STRATEGY is behavioral design pattern. Factory REVOLVES around the creation of OBJECT at runtime whereas Strategy or POLICY revolves around the decision at runtime.

Factory is a creational design pattern whereas Strategy is behavioral design pattern. Factory revolves around the creation of object at runtime whereas Strategy or Policy revolves around the decision at runtime.

Builder is a creational Design Pattern WHEREAS COMPOSITE is a structural design pattern. Composite creates PARENT - Child relations between your objects while Builder is used to CREATE group of objects of PREDEFINED types.

Builder is a creational Design Pattern whereas Composite is a structural design pattern. Composite creates Parent - Child relations between your objects while Builder is used to create group of objects of predefined types.

The Difference between these patterns in only the intent. Adapter is used because the OBJECTS in current form cannot communicate where as in Facade , THOUGH the objects can communicate , A Facade object is placed between the client and subject to SIMPLIFY the INTERFACE.

The Difference between these patterns in only the intent. Adapter is used because the objects in current form cannot communicate where as in Facade , though the objects can communicate , A Facade object is placed between the client and subject to simplify the interface.

 Adapter OBJECT has a DIFFERENT input than the real SUBJECT whereas Proxy object has the same input as the real subject. Proxy object is such that it should be placed as it is in place of the real subject.

 Adapter object has a different input than the real subject whereas Proxy object has the same input as the real subject. Proxy object is such that it should be placed as it is in place of the real subject.

We have multi tier architecture with multiple layers , We have series of WEB servers and applications in application tier, infrastructure libraries at middle tier and Database servers at the LOWER tier. We are USING ORACLE as Database, ESB ( Enterprise service Bus ) for asynchronous communication and Rest Web Services.

We have multi tier architecture with multiple layers , We have series of web servers and applications in application tier, infrastructure libraries at middle tier and Database servers at the lower tier. We are using Oracle as Database, ESB ( Enterprise service Bus ) for asynchronous communication and Rest Web Services.

We as a TEAM of developers , testers , ANALYST , LEAD and architect sit close to each other. Most of the time I would just jump to their SEAT and talk to them ( if required ). We have daily stand up where we discuss things that needs team attention. 

We as a team of developers , testers , analyst , lead and architect sit close to each other. Most of the time I would just jump to their seat and talk to them ( if required ). We have daily stand up where we discuss things that needs team attention. 

USE CASE DIAGRAM, Component Diagram for High LEVEL Design and Class Diagram , Sequence Diagram for low level design.

Use Case Diagram, Component Diagram for High level Design and Class Diagram , Sequence Diagram for low level design.

If its already there in MAVEN local repository, We can add that as a dependency in the PROJECT pom FILE with its Group Id, Artifact Id and version.

We can provide additional attribute SystemPath if its unable to locate the jar in the local repository.

If its not there in the local repository, we can INSTALL it first in the local repository and then can add it as dependency.

If its already there in Maven local repository, We can add that as a dependency in the project pom file with its Group Id, Artifact Id and version.

We can provide additional attribute SystemPath if its unable to locate the jar in the local repository.

If its not there in the local repository, we can install it first in the local repository and then can add it as dependency.

In first case, there would be 2 DB calls in WORST case and 1 in BEST case. In 2nd approach there will be always 2 DB calls.

Decision on the approach should depend on the following CONSIDERATIONS -

1. How costly is the call to DB. Are we using indices , hibernate etc

If calls to DB are costly , 1st approach should be the choice.

2. Exception Book KEEPING load upon exception.

The benefit of SAVING 1st call in approach 1 should be bigger than the Book keeping for the exception.

3. Probability of the exception in first apparoach.

If the DB Table is almost empty, it makes sense to follow Approach 1 as majority of the 1st calls will pass through without exception.

In first case, there would be 2 DB calls in worst case and 1 in best case. In 2nd approach there will be always 2 DB calls.

Decision on the approach should depend on the following considerations -

1. How costly is the call to DB. Are we using indices , hibernate etc

If calls to DB are costly , 1st approach should be the choice.

2. Exception Book keeping load upon exception.

The benefit of saving 1st call in approach 1 should be bigger than the Book keeping for the exception.

3. Probability of the exception in first apparoach.

If the DB Table is almost empty, it makes sense to follow Approach 1 as majority of the 1st calls will pass through without exception.

1. Query Optimization ( Query REWRITING , Prepared Statements )
2.  Restructuring Indexes.
3. DB Caching TUNING ( if using ORM )
4. IDENTIFYING the problems ( if any ) with the ORM Strategy ( If using ORM )

 Lambda Expressions , Interface DEFAULT and STATIC Methods , Method Reference , Parameters NAME , Optional , Streams, CONCURRENCY.

 Lambda Expressions , Interface Default and Static Methods , Method Reference , Parameters Name , Optional , Streams, Concurrency.

1. Set lazy=false in the HIBERNATE config file.
2.  Set @Basic(fetch=FetchType.EAGER) at the mapping.
3. MAKE SURE that we are ACCESSING the dependent objects before closing the session.
4. Using Fetch Join in HQL.

1. First level cache is ENABLED by default whereas Second level cache NEEDS to be enabled explicitly.
2. First level Cache CAME with Hibernate 1.0 whereas Second level cache came with Hibernate 3.0.
3.  First level Cache is SESSION specific whereas Second level cache is shared by sessions that is why First level cache is CONSIDERED local and second level cache is considered global.

SESSION info in the request can be intercepted and hence a vulnerability. Cookie can be read and write by RESPECTIVE DOMAIN only and make sure that right session INFORMATION is being passed by the client.

Session info in the request can be intercepted and hence a vulnerability. Cookie can be read and write by respective domain only and make sure that right session information is being passed by the client.

With the ADVENT of Internet, HTTP is the most preferred way of communication. Most of the clients ( web THIN client , web thick clients , mobile apps ) are DESIGNED to communicate using http only. Web Services using http makes them accessible from vast variety of client APPLICATIONS. 

With the advent of Internet, HTTP is the most preferred way of communication. Most of the clients ( web thin client , web thick clients , mobile apps ) are designed to communicate using http only. Web Services using http makes them accessible from vast variety of client applications. 

When multiple external resources are trying to access the DB locks and runs into cyclic WAIT, it may makes the DB unresponsive. 

Deadlock can be AVOIDED using VARIETY of measures, Few listed below:

• Can make a queue wherein we can verify and order the request to DB.
• LESS USE of cursors as they lock the tables for long time.
• Keeping the transaction smaller.

When multiple external resources are trying to access the DB locks and runs into cyclic wait, it may makes the DB unresponsive. 

Deadlock can be avoided using variety of measures, Few listed below:

Simplest implementation we can have is a List wherein we can PLACE ordered WORDS and HENCE can perform Binary Search.

Other implementation with better search performance is to use HashMap with key as first character of the WORD and value as a LinkedList.

Further level up, we can have linked Hashmaps like ,

hashmap {

a ( key ) -> hashmap (key-aa , value (hashmap(key-aaa,value)

b ( key ) -> hashmap (key-ba , value (hashmap(key-baa,value)

....................................................................................

z( key ) -> hashmap (key-za , value (hashmap(key-zaa,value)

}

upto n levels ( where n is the average size of the word in dictionary.

Simplest implementation we can have is a List wherein we can place ordered words and hence can perform Binary Search.

Other implementation with better search performance is to use HashMap with key as first character of the word and value as a LinkedList.

Further level up, we can have linked Hashmaps like ,

hashmap {

a ( key ) -> hashmap (key-aa , value (hashmap(key-aaa,value)

b ( key ) -> hashmap (key-ba , value (hashmap(key-baa,value)

....................................................................................

z( key ) -> hashmap (key-za , value (hashmap(key-zaa,value)

}

upto n levels ( where n is the average size of the word in dictionary.

Volatile is an INSTRUCTION that the VARIABLES can be accessed by multiple THREADS and hence shouldn't be cached. As volatile variables are never cached and hence their RETRIEVAL cannot be optimized.

Volatile is an instruction that the variables can be accessed by multiple threads and hence shouldn't be cached. As volatile variables are never cached and hence their retrieval cannot be optimized.

The Permanent Generation (PermGen) space has completely been removed and is kind of REPLACED by a new space called Metaspace. The consequences of the PermGen removal is that obviously the PermSize and MaxPermSize JVM arguments are IGNORED and you will NEVER get a java.lang.OutOfMemoryError: PermGen ERROR.

The Permanent Generation (PermGen) space has completely been removed and is kind of replaced by a new space called Metaspace. The consequences of the PermGen removal is that obviously the PermSize and MaxPermSize JVM arguments are ignored and you will never get a java.lang.OutOfMemoryError: PermGen error.

The memory pool containing all the reflective data of the java virtual machine itself, such as CLASS and method objects. With Java VMS that use class data sharing, this generation is divided into read-only and read-write areas. The Permanent generation CONTAINS metadata required by the JVM to describe the CLASSES and methods used in the application. The permanent generation is populated by the JVM at runtime based on classes in use by the application. In addition, Java SE library classes and methods may be STORED here.

The memory pool containing all the reflective data of the java virtual machine itself, such as class and method objects. With Java VMs that use class data sharing, this generation is divided into read-only and read-write areas. The Permanent generation contains metadata required by the JVM to describe the classes and methods used in the application. The permanent generation is populated by the JVM at runtime based on classes in use by the application. In addition, Java SE library classes and methods may be stored here.

Bootstrap - Loads JDK internal CLASSES, JAVA.* packages.

Extensions - Loads JAR files from JDK extensions directory - usually lib/ext directory of the JRE

System - Loads classes from system classpath.

Bootstrap - Loads JDK internal classes, java.* packages.

Extensions - Loads jar files from JDK extensions directory - usually lib/ext directory of the JRE

System - Loads classes from system classpath.

1. Spring enables developers to develop enterprise-class applications using POJOs. The benefit of using only POJOs is that you do not need an EJB container product.
2. Spring is organized in a modular fashion. Even though the number of packages and classes are substantial, you have to worry only about ones you need and ignore the rest.
3. Spring does not reinvent the wheel instead, it truly makes use of some of the existing technologies like several ORM frameworks, logging frameworks, JEE, Quartz and JDK timers, other view technologies.
4. Testing an application written with Spring is simple because environment-dependent code is moved into this framework. Furthermore, by using JavaBean-style POJOs, it becomes easier to use dependency injection for injecting test data.
5. Spring’s web framework is a well-designed web MVC framework, which provides a great alternative to web frameworks such as Struts or other over ENGINEERED or less popular web frameworks.
6. Spring provides a convenient API to translate technology-specific exceptions (thrown by JDBC, Hibernate, or JDO, for example) into consistent, unchecked exceptions.
7. Lightweight IoC containers tend to be lightweight, especially when compared to EJB containers, for example. This is BENEFICIAL for developing and deploying applications on computers with limited MEMORY and CPU RESOURCES.
8. Spring provides a consistent transaction management interface that can scale down to a local transaction

Class , Heap , STACK , REGISTER , Native METHOD Stack.

Class , Heap , Stack , Register , Native Method Stack.

No, Java runs on a virtual machine CALLED JVM and HENCE doesn't embed well with the underlying hardware. Though we can CREATE a PLATFORM independent system software but that WOULD be really slow and that's what we would never need. 

No, Java runs on a virtual machine called JVM and hence doesn't embed well with the underlying hardware. Though we can create a platform independent system software but that would be really slow and that's what we would never need.