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. |
|
|||
|
| ||||
| Design - Interview Questions and Answers for 'Convention over configuration' - 3 question(s) found - Order By Rating | ||||
| ||||
| Ans. Hibernate mapping configurations are used for mapping hibernate entities and corresponding DB Tables. Conventionally Entities and Table can share the same name and hence framework can provide implicit mapping instead of explicit mapping through configurations. Though it may result in little loss of flexibility in extreme cases but will work with all applications following the convention. | ||||
| Help us improve. Please let us know the company, where you were asked this question : | ||||
 Discuss Correct / Improve  Convention over configuration | ||||
 Related Questions | ||||
 What is "convention over configuration" ? Which framework uses this design paradigm ? | ||||
| Are there any disadvantages of "Convention over configuration" Design paradigm ? | ||||
| ||||
| Ans. Yes, It may result in some loss of flexibility as the application has to follow all conventions. Moreover it can contradict with other design paradigms or principles used in the application or framework. | ||||
| Help us improve. Please let us know the company, where you were asked this question : | ||||
| Discuss Correct / Improve Convention over configuration | ||||
| Related Questions | ||||
| What is "convention over configuration" ? Which framework uses this design paradigm ? | ||||
| Can you give an example of "Convention over configuration" Design principle ? | ||||
| ||||
| 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 : | ||||
Discuss Correct / Improve Convention over configuration  Asked in 1 Companies | ||||
| Related Questions | ||||
| Are there any disadvantages of "Convention over configuration" Design paradigm ? | ||||
| Can you give an example of "Convention over configuration" Design principle ? | ||||
