Most software applications require persistence programming of some kind—but what exactly is it, and more importantly, are we doing it right?
A few years ago, my team was working on a commercial Java development project for Enhanced 911 (E911) emergency call centers. We were frustrated by trying to meet the data-storage requirements of this project using the traditional model of Java over an SQL database. After some reflection about the particular requirements (and non-requirements) of the project, we took a deep breath and decided to create our own custom persistence layer from scratch. This ended up being a lot of work, but it also gave us a chance to rethink persistence programming in Java.
This was a good article on optimizing persistent storage for a specific language like Java. One caveat is that the approach can cause problems if you later need to support other languages. At work we use a mix of Java, C#, PHP for different services and they sometimes need to share a database.
Displaying 1 comment