Skip to main content

Integration Project- Micro Services Migration Story with JBoss BPM Travel Agency - Part Two

Part two - Moving towards Microservices


Recently "microservices" has become a popular phenomena in application development, if you google it, you will find hundreds definition, best practice and design patterns on this new software architecture. To me, this is not new, back on the "SOA" days, I found the hardest thing for us, is to decide the granularity of the services. That is, deciding how much data each service needs to provide, without wasting too much resource in each client call, or have tiny services that client needs to orchestrate and manage everything. For many "political" reasons, we weren't able to provide service with reasonable size, they needs to be huge with loads of business logic. At the time "Monolithic Applications" was the mainstream way of application development and deployment. As a developer, we hated the decision, because it would involve too many people to just push out one service releases. We came up with an idea of breaking the services down into many modules, and each module simply does very simple functions. We had no choice because it would be a headache to manage the team of eight, and having them wait for each other. The way we implement it, is through use of EJB call, can dependency JARs. As it's still deployed as on big monolithic applications, scaling part of the service became a problem. The only thing we can do it to added more server running the application. At the time, we had the idea of micro services, it's just the technology just isn't complete to support us. Now that application container became lightweight, it's cheap to spin up one and having it just run one single task. And with the fast computing power, and simple data exchange format like JSON, now it's alright to make service call asynchronize, there are many advantages when it's asynchronized. Might cover that in other post. So when I see the travel agency project, I think it is a great example to show how micro services can be done using JBoss Fuse.


The Travel Agency Demo showcase a business process for a user to request a holiday itinerary, it'll look up the available flight and hotel, and booked the flight and hotel respectively, if the credit card is invalid, it will cancel the booking. The original application was in JavaEE, everything is all packaged and wrote in the same package. It'll face the problem when it tries to scale-up any of the services.

During the re-construction , I want to make sure it does not impact the original business flow. So it's provide the same services as it is. OK, now we start moving to microservice. First of all, breaking down to smaller pieces, because Flight and Hotel are in nature different services, so I separate them in two. In the application, it has web service endpoints to talk to BPM Suite or other client, and at the backend, the available data and booking data are stored in a Database. In between front and backend, I decide to make the communication async, so it's easier to scale-out and make sure it's absolutely decoupled, and language independent.
For backend, it needs to provide 3 different functionality,
  1. Recommend 1 available Flight/Hotel 
  2. Book and record Flight/Hotel 
  3. Cancel previous booking of Flight/Hotel 
You would think I'll break them into 3 services, and deploy them separately into different container right? Nope! I am not going to do it ,this time. Instead, I'll be breaking them into 2 projects, one give a promoted recommendation of hotel/flight, the other handles booking and canceling. The reason business-wise, putting booking and cancellation together is they logically belong together, you need the booking number to cancel a booking, if anything changes to booking, then it may alway impact cancellation. And technology-wise because I use JDBC to retrieve the list, and JPA for both Booking and Cancellation, so the configuration are shared for both booking and cancellation. That's why I want to group them together.

 

It is very easy for people to over-do the microservice, for me it's not all about breaking down service to make it do one thing per service, but to make it easier for developer to maintain and make sense logically. But what if one day booking and cancellation needs to separate? Don't worry, one thing JBoss Fuse is great to implement microservice is the way we can break different functions into different Camel routes. So when it's time to separate them, it's simply the matter of moving the route to another project.


(Project contains 2 routes, booking and canceling)

(Booking route)

(Cancel Booking route)

This is how I move the monolithic application to a more microservice approach. Now it's going to be much easier to scale out, and the application will have less impact to other application if anything goes wrong. From the diagram, you can see now, we can add a gateway in front to dispatch loads to the two containers listening and waiting for incoming request, and have messaging broker to serve as another layer of buffer.


OK, enough of the architecture talk, next time, we'll take a look at how to migrate web service to JBoss Fuse. (Contract-first Web Service in Camel).

For more detail side in BPM Suite, please click here to Eric Schabell's post.

Micro Services Migration Story with JBoss BPM Travel Agency
Part One: Introduction and Installation
Part Two: Moving towards Microservices

Comments

Popular posts from this blog

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …

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 …