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 Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.

=======================正文=======================

這個題目很多人叫我寫,可是這題目好大,這分明就是整死我咩~
所以我會分幾段慢慢寫。

JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

Connection Pool 最多可以開啓的 connection 數量

prefill

事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。
加上…

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …