Most enterprises today are application centric. But the problem with the application is that their database schemas, user interfaces, programming interfaces and object models are tightly coupled and difficult to change. If you want to add a new field to a database table and you’re lucky, the change will reflect through the entire system. But often the change needs to be replicated manually across the entire system. And as applications are difficult to change, adding business rules or process to the application does not facilitate business agility. This is where layered architecture comes...

I do a lot of Java coding and I enjoy it. I admit that there is a lotof typing, often a lot of boilerplate and getting even simple tasksdone can involve too much work. Most of the tools that try to fixthese problems trade one moment saved for another lost. Maven's XMLbased configuration file is a good example: Thank you for making myproject easier to manage and I won't forget that you made me edit XMLto do so.These are the things that you live with, these are the things youtrade for using a language that thinks it's finishing what C++started; a language that is loved equally by mammoth corpora...