This article shows the different components available for a Hybrid Integration Architecture. The goal is not to discuss different vendor offerings but to explain different concepts and benefits of each component in general and how they relate to each other. Including concepts such as Hybrid Integration Platform (HIP), Cloud-Native Middleware, PaaS, Docker, iPaaS, iSaaS, API Management, and others.
This article discusses how relevant microservices, containers and a cloud-native architecture is for middleware. It is unbelievable how fast enterprises of all sizes are moving forward with these topics!
This article discusses my talk at JPoint in Moscow about: “Microservices, Containers, Docker and a Cloud-Native Architecture in the Middleware World”.
In 2015, the middleware world focuses on two buzzwords: Docker and Microservices. Software vendors still sell products such as an Enterprise Service Bus (ESB) or Complex Event Processing (CEP) engines. How is this related? This session discusses the requirements, best practices and challenges for creating a good Microservices architecture, and if this spells the end of the Enterprise Service Bus (ESB).
These days, I am at JavaOne 2012 in San Francisco. That’s the largest and most important Java conference worldwide. In this blog post, I wanna share the slides of my two talks…
“Cloud Computing Architected – Solution Design Handbook” by John Rhoton and Risto Haukioja was published by Recursive Press in May 2011. This book is a great addition to other books about cloud computing.
The integration framework Apache Camel already supports several important cloud services. This article describes the combination of Apache Camel and the Amazon Web Services (AWS) interfaces of Simple Storage Service (S3), Simple Queue Service (SQS) and Simple Notification Service (SNS). Thus, The concept of Infrastructure as a Service (IaaS) is used to access messaging systems and data storage without any need for configuration.