• Proprietary middleware stack (IBM, BEA, Microsoft, Oracle etc)
• Open-source software (often Linux, Apache, MySQL and Perl/Python/PHP; referred to as the LAMP).
We have had very negative experience with JAVA EE-application servers, like IBM WAS (WebSphere Application Server) and its ESB implementation (Enterprise Service Bus). JEE has traditionally been a path to vendor lock-in even though specifications are free and open. We feel this has led us to the recommendation to avoid application server dependencies. This, in turn, has led us to a server solution based on the open-source servlet containers Jetty and Tomcat. The idea behind ESB did not fit our demands properly and instead we based our architecture on a simple single database message poll solution, and various other integration techniques.
It has proven difficult to find an open-source project with a level of customization and functionality to match the requirements for this architecture. Therefore Nets has developed an Java library (core-proxy), and will in the future provide this as a contribution to the open-source community as free software.
