Design - Interview Questions and Answers for 'Lazy vs eager loading' | Search Interview Question - javasearch.buggybread.com
Questions
Search
List By Company
List By Topic
Legacy
Tests
Repository
DashBoard
Java
Java 8
Java 7
Java Abbreviations
OCJP / SCJP
Class List
New in Java 8
Java Exceptions
Spring Exceptions
Java Enums
Java 8 Lambda
Java 8 java.time
Big Data
Best Of Java
Discussion
Search
Subscribe
Search Interview Questions
More than 3000 questions in repository.
There are more than 900 unanswered questions.
Click here
and help us by providing the answer.
Have a video suggestion.
Click Correct / Improve and please let us know.
Label / Company
Label / Company / Text
Search
Submit Question
Design - Interview Questions and Answers for 'Lazy vs eager loading' - 1 question(s) found
- Order By Newest
Q1.
If you are given choice to either load object eagerly or lazily , which one would you use in case of singleton pattern ?
Design
Ans. I would choose Eager as the cost for 1 additional object is too minute for any such consideration.
Eager Loading results in Faster access ( Object available at load time) at the cost of additional space.
Lazy loading results in space saving ( Object available at first use ) at the cost of access speed.
Help us improve. Please let us know the company, where you were asked this question
:
Like
Discuss
Correct / Improve
 design Pattern  Singleton  Lazy vs Eager Loading
Correction
Duplicate of Another Question
Company where this question was Asked
Suggestion
Related Questions
Difference between Static and Singleton Class ?
What is the difference between Singleton and Prototype Bean scope in Spring ?
serialization and deserialization of singleton class
What is the difference between these two approaches of creating singleton Class ?
//Double Checked Locking Code
public static Singleton createInstance() {
if(singleton == null){
synchronized(Singleton.class) {
if(singleton == null) {
singleton = new Singleton();
}
}
}
return singleton;
}
//Single checked locking code
public static Singleton createInstance() {
synchronized(Singleton.class) {
if(singleton == null) {
singleton = new Singleton();
}
}
return singleton;
}
What are design situations to use Singleton and Prototype Design Pattern ?
How to avoid cloning, serialization in the singleton class ?
When singleton can break and how to resolve it
When should we use prototype scope and singleton scope for beans ?
Explain Singleton Design Pattern ?
Help us and Others Improve. Please let us know the questions asked in any of your previous interview.
Any input from you will be highly appreciated and It will unlock the application for 10 more requests.
Company Name:
Questions Asked: