Skip to main content

Fuse Integration Service - Auto Dealership Management Demo, Part Five

This series of blog is based on building an auto dealership management system on Fuse Integration Service. We will be creating three major functions in the system.
  • Sales report tracking 
  • Vehicle inventory status
  • Customer IoT Service
We have exported a sales report to a web page, provide current inventory status of available cars through web service. And collect customer data from IoT devices on their car then alert close by shops. Now all the application are up on OpenShift, here are some of the things we will face after our application leave developer's laptop onto testing, production phase. With the new Fuse Integration Service, it is now really easy to package and startup and shutdown running instance, so we can update more frequently. But when it comes to clients trying to connect to the service, maybe this is not a great news to them, all these constant start up and shutting down, what happen if they are in the middle of a request? 

Here is a neat thing in Fuse Integration Service, instead of forcing every pod/instance to shutdown and running the new application instantly, we can do rolling upgrades. Yes, I am going to show you how to do rolling upgrades with our fabric8 maven plugin. 


Before we get to the "how", lets take a look at what does rolling do. Normally when we do fabric8:apply, what it does, is pushing the application onto our project in OpenShift, and then it'll quickly spin up a new pod/instance running the updated application, and simultaneously kills the old running pods/instances.  But for rolling upgrade, it does things a little different. 

First of all, it will spin up pods/instance running the updated application, 

Instead of killing all the old running pods instantly, it will slowly terminate each pod that does not have any connection, and new incoming request will be redirect to new application pods. 
With this scenario, client still in transaction will not suddenly break out from it, and new client request will go to the pods that will continue to run. 

Slowly the updated application will be replace with new running pod. 

So, how do we do rolling upgrade? Simple, simply add fabric8.rolling=true when running fabric8:apply in maven. 

  • mvn fabric8:apply -Dfabric8.rolling=true

And that's all you have to do! Simple! 


Blogger said…
Did you know you can shorten your urls with AdFly and earn $$$$$ for every visitor to your short urls.

Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …