Monday, July 17th, 2006
A funny thing happened a few years ago in the Java community. Architectures were so complicated that myriads of patterns were born just to make them work (major contributor: Enterprise JavaBeans).
At first developers though we needed these “enterprise” features, so they went along with it all. Then the complexity shone through after a few years of failed projects and “huh?” moments. People were sick of having to create Session Facades, Value Objects and Fat Primary Keys to try to get around performance failings. You ended up with 20 objects when you just needed 1 :)
Then a set of previously burned developers got together to create simpler frameworks, and the term “POJO” (Plain Old Java Object) was born. That is right, things got so complex that you needed a way to say “No mate, we just want a normal object here”. “But what about the Entity Bean? and the Home interface, and the Remote interface, and the Facade, and the”. “NO. POJO”.
Posted by Dion Almaer at 4:01 pm