After three great years at TIBCO Software, I move back to open source and join Confluent, the company behind the open source project Apache Kafka to build mission-critical, scalable infrastructures for messaging, integration and stream processsing. In this blog post, I want to share why I see the future for middleware and big data analytics in open source technologies, why I really like Confluent, what I will focus on in the next months, and why I am so excited about this next step in my career.
I want to share my slide deck and video recordings from the talk “10 Lessons Learned from Building Cloud Native Middleware Microservices” at O’Reilly Software Architecture April 2017 in New York, USA in April 2017.
This blog explains the different components of a hybrid integration architecture, their deployment models, when to use them, and their target audience. Afterward, each section shows how TIBCO’s Hybrid Integration Platform maps to this.
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.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.