An Oracle blog about Java Technology

Java SE 8 and Java EE 7 in Production at TecSinapse

Guest Author

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. A nice adoption story presented at JavaOne 2016 was from TecSinapse. The session was presented by Michael Santos.

For those unaware, Michael Santos is an active member of the Brazillian Java community. He is a Java Champion, JavaOne Rock Star Speaker, blogger, OpenJDK committer, JCP expert and open source advocate. Michael is part of SouJava's board - one of the largest and most influential JUGs in the world. As head of development and operations at TecSinapse he oversaw real world adoption of both Java SE 8 and Java EE 7 in customer projects. TecSinapse is a consulting, solutions and integration provider out of Brazil. Some of their clients include Audi, Mercedes-Benz, Harley-Davidson, Jaguar, Land Rover, Nissan, Toyota and BMW. At JavaOne Michael provided specific insights on how he used Java EE 7 and Java SE 8 together. He also did not shy away from pointing out where Java SE and Java EE integration should improve. You can view his very 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.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.