Navigating the Java mapping landscape – evaluating framework trade-offs
You can now understand the motivations for using layers. It’s great that we have a mature Java ecosystem and don’t have to do everything manually – thanks to the frameworks. Since there are so many of them, we can categorize them based on API usability, proximity, and runtime.
- Usability: One of the items to evaluate when looking at a framework is the usability of its API. For instance, you can ask a question such as “How many times can we use the same API with different databases? Is it even possible?”
- Agnostic API: A single API can be used with multiple database vendors, types, or paradigms. The positive aspect of this is that an agnostic API reduces the cognitive load since you don’t need to learn about a new API for every different database integration. However, you might lose particular database behaviors or have to wait longer to receive feature updates...