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.
The following shows a case study about successfully moving from a very complex monolith system to a cloud-native architecture. The architecture leverages containers and Microservices. This solve issues such as high efforts for extending the system, and a very slow deployment process. The old system included a few huge Java applications and a complex integration middleware deployment.
The new architecture allows flexible development, deployment and operations of business and integration services. Besides, it is vendor-agnostic so that you can leverage on-premise hardware, different public cloud infrastructures, and cloud-native PaaS platforms.
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
[This article was posted some time ago on the TIBCO Blog, already. I also added some information about BusinessWorks Container Edition (BW CE) where appropriate. Most of the characteristics defined below are true for both, BW6 and BW CE]
TIBCO ActiveMatrix BusinessWorks 6 (BW6) 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:
I was invited to speak at Microservices Meetup Dublin this week. I updated my slide deck “Microservices – Death of the ESB?” … The meetup was fully booked with a waiting list; around 120 attendees came to Gild‘s office. (see attached link).
If you have not seen the slide deck last year, you should definitely take a look at this updated version with more recent information. I also incorporated valuable information from discussions with attendees in 2015’s sessions about this topic.
Docker is one of the hottest technologies right now.
Relation to SOA, ESB and Microservices
Many TIBCO customers already ask how they can leverage Docker in combination with SOA, ESB and Microservices, and what TIBCO’s strategy is. I just want to refer to an article I published recently, it shows some insights about TIBCO’s future strategy from the Docker perspective:
The following shows a snippet of the article, which explains how Docker is related to Microservices.
[UPDATE June 2016: Please also read this updated article about Microservices, Containers and Cloud-Native Architecture for Middleware]
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?
Docker is a fascinating technology to deploy and distribute modules (middleware, applications, services) quickly and easily. Most people agree that Docker will change the future of software development in the next years. I will do another blog post about how Docker is related to TIBCO and how you can deploy and distribute Microservices with Docker and TIBCO products such as TIBCO EMS and BusinessWorks 6 easily.
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.
TIBCO BusinessWorks and StreamBase for Big Data Integration and Streaming Analytics with Apache Hadoop and ImpalaPosted in Analytics, Big Data, Business Intelligence, Hadoop, In Memory, NoSQL on April 14th, 2015 by Kai Wähner
Apache Hadoop is getting more and more relevant. Not just for Big Data processing (e.g. MapReduce), but also for Fast Data processing (e.g. Stream Processing). Recently, I published two blog posts on the TIBCO blog to show how you can leverage TIBCO BusinessWorks 6 and TIBCO StreamBase to realize Big Data and Fast Data Hadoop use cases.