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.
|Interview Questions and Answers|
|Ans. Convention over configuration is a way of software design used by frameworks that attempt to decrease the number of decisions that a developer is required to make without necessarily losing flexibility. The objective is to reduce the unnecessary configurations and follow conventions to accomplish that. For example - DB Entity and DB Table name conventionally should be same and hence shouldn't require configuring mapping between the two.|
"Spring Boot" and "Ruby on Rails" have adopted this design principle.
|Help us improve. Please let us know the company, where you were asked this question :|
|Like Discuss Correct / Improve  Convention over configuration Asked in 1 Companies|
|Are there any disadvantages of "Convention over configuration" Design paradigm ?|
|Can you give an example of "Convention over configuration" Design principle ?|