Why was Sidekar created?
Because sometimes you just need something simple, fast, and elegant 🙂 Of course, no tool is perfect — and every tool has it’s “target market”. If you have a real need to store Java persistent data in an SQL database, tools like Hibernate help you do that. However, sometimes we use tools just because they are there, and only later realize that doing so has several drawbacks. Storing Java data in an SQL database has many hidden costs, such as: • The well-documented Object-relational impedence mismatch. • So many layers between your code and the underlying persistent data it’s hard to debug problems • Lack of clarity around how to design your queries and your schema to be efficient • Unnatural/broken mapping between Java semantics and database transaction isolation levels • Annotation insanity Sidekar was designed to provide “real” Java persistence but with minimal distraction to the programmer. Sidekar seeks to provide a cleaner, simpler, and easier to understand way to persist data i
