Like every year, I attended JavaOne (part of Oracle World) in San Francisco in late September 2016. This is still one of the biggest conferences around the world for technical experts like developers and architects.
I planned to write a blog posts about new trends from the program, exhibition and chats with other attendees. Though, I can make it short: Besides focus on Java platform updates (Java 9, Java EE 8, etc.), I saw three hot topics which are highly related to each other: Microservices, Docker and Cloud. It felt like 80% of non-Java talks were about these three topics. The other 20% were Internet of Things (IoT), DevOps and some other stuff. Middleware was also a hot topic. Not always directly, but I was in several talks focusing on integration, orchestration of microservices, (IoT) gateways.
My Talk at JavaOne 2016: Cloud-Native Microservices and Containers in the Middleware World
No surprise that my talk this year also focused on these hot topics – specifically focusing on middleware. However, the focus was a different one than most other presentations: I talked about the journey, which middleware has to undergo these days.
I discussed the move from a classical middleware – often called Enterprise Service Bus (ESB) – to cloud-native middleware microservices. This sessions explained the relation to new concepts like Docker containers, DevOps, and modern open source cloud platforms like CloudFoundry, Kubernetes or Apache Mesos.
Interesting side note: Some attendees asked me: “Is middleware even needed after everybody moves to microservices”? I get the same question often. Not just at conferences, but also from customers.
One of these guys already answered the question by himself before I could respond: “Well, as there are so many independent microservices, different technologies, cloud services and edge devices like IoT, I think the answer is YES, there is still a need for middleware, right?!”.
I added to this: “I can assure you: The answer is YES. You need even more middleware than before. You need to interconnect everything! Within your enterprise, remote edge IoT devices, partner services, with cloud services, and also open it up for the external world, i.e. users you do not even know today…
However, middleware changed in the last years. It is not the heavyweight central platform anymore, but a hybrid integration platform, which serves all the various use cases and different audience (like integration specialists, ad-hoc integrators, and even business users). The tooling got more lightweight, and cloud-native!
In addition to focusing on many related concepts, technologies and cloud platforms, my session also discussed ten lessons learned from building cloud-native middleware microservices together with our customers in the last months:
I will publish a more detailed post about these 10 lessons learned soon.
Here is my slide deck from my JavaOne presentation:
Click on the button to load the content from www.slideshare.net.
The following 20min live demo shows how to deploy a single (i.e. built just once) TIBCO BusinessWorks Container Edition microservice to different cloud and container platforms: Docker, Kubernetes and Pivotal CloudFoundry. The video also shows how to leverage other cloud-native open source frameworks such as Consul and Spring Cloud Config for distributed configuration management and service discovery of middleware microservices.
As always, I appreciate any comments or feedback…
Batch processing introduces delays, complexity, and data quality issues that modern businesses can no longer…
Modernizing legacy systems doesn’t have to mean a risky big-bang rewrite. This blog explores how…
Retail media is reshaping digital advertising by using first-party data to deliver personalized, timely ads…
Legacy OT middleware is struggling to keep up with real-time, scalable, and cloud-native demands. As…
The CIO Summit in Amsterdam provided a valuable perspective on the state of AI adoption…
Cathay Pacific is evolving beyond aviation, rebranding as Cathay to offer a seamless travel and…