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 in the coming months. A particularly nice adoption story presented at JavaOne 2016 was from Scytl. The session was presented by Alex Soto.
Scytl is a very innovative and important company that enables secure online voting across the world. Alex was the architect of a service-only back end system at Scytl written using vanilla Java EE and TomEE. Alex talked about the reasons they chose Java EE (over Spring in this case) such as ease-of-use, productivity, simplicity, standardization, lack of third-party dependencies, simple deployment, fast startup and performance. He also discussed their use of some pretty cool TomEE features, Arquillian, Docker and Apache Mesos. For those unaware, Alex is a Java EE advocate, blogger, author, JCP expert and open source commiter. You can view Alex's well-rated 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.