Skip to main content

Red Hat JBoss Fuse - Managing microservice architecture in JBoss Fuse

Moving away from a monolithic application towards microservice architectures, that means the application goes from a centralized big bulk of package deploy on single instance, to small modularized chunk deploy on multiple distributed environment. As mircoservice brings you the advantages of easier to maintain the code, and allowing more developer to work simultaneously, but it also comes with additional problems like a more complex environment, and become difficult to manage.

It will be very irritating to check every single instances, so it's important to have a centralized view of the entire environment, and have that summarized. In JBoss Fuse, we uses something called Insight, which consolidate view on both the log and Camel events, so you have better idea of what is going on in your system in a broader view. By default JBoss Fuse collects data into Easticsearch. It is a is a powerful search engine, which handles distributed datasource efficiently with Restful interface open for query. By taking advantage of the fast search ability, we can store and load the log and camel metrics content. Have data is not enough, without a proper display view, it is also just a bunch of text, and numbers. In JBoss Fuse, we uses Kibana is the search dashboard for Elasticsearch, which analyze the data, display the query result. 


Enabling the Insight is pretty easy, First of all, we need to create a few container to act as the distributed datastore for the instance, please locate a large amount of memories for these instance, as the algorithm requires loading indexes in memory for calculations. I am creating more then one datasource instance because I would like to have HA clusters for these data. 


And add the Insight console (Kibana) profile to the root container, also add the log and camel metrics profile too to also collect data from root. 


Once the profile is installed, you will find the Insight view on the top lefthand corner, click on it, 


Here are the dashboard consolidated view on log and camel metrics of the entire fabric, for the managements to see. 



And under Elasticsearch tab, it shows how the data are distributed

To run an example, I am going to create 2 running instances (containers), deploying a basic camel example writing logs in every 5 seconds. To start collecting data, please also add the insight-log and insight-camel to the container. 




Once all container started, 

Go back to the Insight view and you will see under Logs tab, all the logs in the fabric are collected. 

And the camel events are picked up as well. 


By having this centralized view, we can see the distributed instance in one single view, making it easy to manage just like what we used to do in monolithic application.

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 …