Cloud-to-Cloud integration is part of a hybrid integration architecture. It enables to implement quick and agile integration scenarios without the burden of setting up complex VM- or container-based infrastructures. One key use case for cloud-to-cloud integration is innovation using a fail-fast methodology where you realize new ideas quickly. You typically think in days or weeks, not in months. If an idea fails, you throw it away and start another new idea. If the idea works well, you scale it out and bring it into production to a on premise, cloud or hybrid infrastructure. Finally, you make expose the idea and make it easily available to any interested service consumer in your enterprise, partners or public end users.
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.
TIBCO ActiveMatrix BusinessWorks 6 is a modern integration and service delivery platform ready for modern concepts such Mobile, Cloud, Internet of Things or Microservices. This article is no introduction to integration and service delivery platforms in general, but focuses on differentiators of BusinessWorks 6 compared to other integration solutions available on the market. If you want to see a general introduction to TIBCO ActiveMatrix BusinessWorks 6, explaining its basic concepts and capabilities such as:
- zero-coding process designer for quick implementation, testing, and maintenance
- distributed scalability for mission-critical systems and ultra-high performance
- standards-based service and application integration
Last week, I gave a talk at a German conference (Karlsruher Entwicklertag 2015) about Microservices. The following slide deck shows plenty of different technologies (e.g. REST, WebSockets), frameworks (e.g. Apache CXF, Apache Camel, Puppet, Docker) or tools (e.g. TIBCO BusinessWorks, API Exchange) to realize Microservices.
Abstract: How to Build Microservices
Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently. This way you get shorter time to results and increased flexibility.
In October 2014, I had a talk at Jazoon in Zurich, Switzerland: “A New Front for SOA: Open API and API Management as Game Changer”
Business Perspective – Open API and API Management
Open API represent the leading edge of a new business model, providing innovative ways for companies to expand brand value and routes to market, and create new value chains for intellectual property. In the past, SOA strategies mostly targeted internal users. Open APIs target mostly external partners.