Markus Eisele is a Java Champion, former Java EE Expert Group member, Java community leader of German DOAG, founder of JavaLand, reputed speaker at Java conferences around the world, and a very well known figure in the Enterprise Java world. He works for Lightbend.
You’ve known and seen him at different conferences and Java User Groups meetups or read his blogs or are following his social media presence. While talking about middleware for many years you’ll continue to hear him talk about enterprise grade Java going forward. Focussed on education about the latest trends in building enterprise systems in a reactive way with Java.
He’s been looking into containers and microservices architectures more deeply and also wrote a book about modern Java EE Design Patterns with O’Reily. He is excited to educate more about how microservices architectures can integrate and complement existing platforms, and will also talk about how to successfully build resilient applications with Java.

How Would ESBs Look Like If They Were Done Today

Looking past the former hype topics like enterprise application integration and ESBs and SOA and alike: Fact is, that the need for reliable integration solutions which are manageable and scalable is growing. More devices and data-sources combined with new and upcoming use-cases and exciting wearables in a cloudified and heterogeneous infrastructure require more bits and pieces than just a central ESB with some rules and point to point connections. How would that look like? And how to keep this kind of solutions manageable?

Take Apache Camel to the Cloud with Fuse on OpenShift

Apache Camel is more than just an integration framework. It is the heart of many modern micro-services infrastructures. In this workshop I am going to walk you through a pre build demo about a investment bank scenario where we are going to manage investment funds. We are trying to modernize our infrastructure by utilizing an event-driven architecture to process new funds when they get created. However, on of our business partners can’t/won’t update their communication strategies, so we’re stuck with trying to modernize within some constraints. All this is going to happen with the help of JBoss Fuse utilizing different contained components like Apache Camel, A-MQ and others to build and change an application with the JBoss Developer Studio and deploy the example on OpenShift.