By reza_rahman on Feb 22, 2016
One of the most important things to do at this stage of the life-cycle of Java EE is highlight successful adoption stories at a regular cadence. We have been doing just that for a long time through our adoption stories blog, this humble blog as well as JavaOne. Indeed JavaOne 2016 was particularly good in this regard. We had a number of solid adoption stories submitted that we could select from. We will highlight all of those stories here. A very nice adoption story presented at JavaOne 2016 was from the TAS Group. The session was presented by Andrea Folli, the CTO of the cashless business unit of the TAS group that recently re-architected their legacy systems using Java EE 7.
The TAS Group is a very important player in back-end e-payment solutions worldwide and certainly in Italy/Europe (so think the folks that do the actual heavy lifting behind e-commerce credit card processing, in-store credit card readers and bank ATMs). The Italy based company has 15 years of experience in providing mission-critical infrastructure for some of the largest financial organizations in Italy and the EU. They manage over 100 million cards world-wide. Over 65% of acquiring systems and more than 50% of issuing systems in Italy alone are managed by them. The company's legacy systems had been written with a combination of COBOL, Spring and J2EE. They successfully migrated these legacy systems to Java EE 6 and now Java EE 7. In adopting Java EE, Andrea cited standardization, portability, vendor neutrality, lack of third party dependencies and runtime performance as some of the reasons. Besides Java EE 7 APIs like JSF, CDI, EJB 3, JPA, JAX-RS, JAX-WS, batch and JTA he noted the use of Eclipse, Maven, Subversion, soapUI, trac and SonarQube. Although he did not name them specifically Andrea touched upon concepts like microservices, reactive architectures and Domain-Driven Design (DDD) using Java EE during his talk. He also shared some very cool Java EE best practices he discovered for his use cases along with cool architectural insights for e-Payment processing. You can view his well-delivered session below (click here if you are having trouble seeing the embedded video).
If you have a similarly great Java EE adoption story to share with the community (particularly migration stories from other technologies), please do feel encouraged to reach out. In the spirit of Java EE centric vendor neutrality, what Java EE implementation or tool set you choose does not matter at all and neither does which part of the globe you are in.