Let's face it, change is the way of life. Inevitably, change is the way of software too. In case of enterprise applications change is continuous. This comes in the form of new business requirements involving complex logic and changes to the interfacing systems. Logic can change on its own and usually does not cause changes to interfacing systems. But the other way round is a completely different story. It is an extremely bad practice to let interfacing systems' scheme (classes and relationships) to propagate through your application. No one does that, no one should. We depend on the use of Adapters, DAO and Value Objects that carry data through our applications and let our logic run on those. Yet, one complexity lingers, how to safely and easily move from one interface to an alternate one. Say today our application uses a traditional relational database like Oracle and we want to replace it with a NoSQL database like MongoDB or Riak or Cassandra? Changes to value ob...
Junked my old tech blog. Here I plan to write about topics relevant to real world implementation of enterprise applications.