Results matter. Choosing a technology stack shouldn’t be an either/or discussion. Thankfully, when it comes to the industry’s two largest enterprise application platforms—Java EE and Spring—architects can cherry pick and integrate with ease. Markus Eisele and Joshua Long explain how architects and developers can benefit from the best of both technologies and embrace cloud-ready JVM architectures. In a hands-on workshop, Markus and Joshya outline five steps for implementation through discussion and exercises:
Step 1: Java EE first, Spring second
Step 2: Spring first, Java EE second
Step 3: Building a bridge between platforms
Step 4: Integration and microservices
Step 5: Missing pieces and wrap-up
Markus and Joshua will take part in Office Hours on Tuesday, April 12 at 12:15 PM in the Mercury Complex. Come by and meet them!
Markus Eisele is a developer advocate at Lightbend. While focused for many years on middleware, today, he’s concentrating on enterprise-grade Java and on education about the latest trends in building enterprise systems in a Reactive way with Java. Markus has also been looking into containers and microservices architectures more deeply. He is a Java Champion, former Java EE Expert Group member, a Java community leader of the German Oracle user group (DOAG), founder of JavaLand, reputed speaker at Java conferences around the world, and a very well-known figure in the enterprise Java world—maybe you’ve seen him at conferences and Java user group meetups, read his blog posts, or follow him on social media. Markus wrote a book about modern Java EE design patterns for O’Reilly and is excited to continue to demonstrate how microservices architectures can integrate and complement existing platforms, as well as how to successfully build resilient applications with Java.
Josh Long is the Spring developer advocate at Pivotal.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com