Skip to main content

Red Hat JBoss Fuse - Processes and Integration routes

People often confuse when they look at camel route and BPM process, although they do look very similar as connecting different nodes with conditions and passing objects or messages, the way they are structured and engineered to execute is a complete different story. Let’s talk about Camel route in JBoss Fuse, the endpoints of camel routes are smart, they handle different protocols, consumes and produce messages, BPM endpoints tends to be just a starting point kick of by a automated application and ended when the process is done. The users of Camel route are more developer oriented it is used to integrate between various systems, routing data and transform messages, whereas BPM are used to describe business process between departments, define business users and departments and are often used by business analyst.

One thing I found when designing integration solutions, I will try to make my services stateless, so it will be more decouple and modularized and easier to horizontally extend the capability. But in a business automation or human tasks, it must keep the state of each process, I made a table showing the difference between the two.

BPM Process
Camel Routes
Main purpose
Describe business processes within an organization
Describe the protocols, transformation of data and integration pattern of a service
Business analyst 
Integration developers
Define business user and department entity
Define systems applications
Divide the node into services in each departments and responsibility
Divide nodes into different actions of a services, such as executing business logics, data transformations
Indicator Only
Smart Endpoint
No, error should be handle by triggering different events
Transactions and XA transactions are supported in Messaging in Database protocols
Human interactions
Built-in Human Task handler
Should avoid human interactions
Best Practice
Place for meaningful business process and business rules
Should only have routing logic, data transform rules. NO business rules in ESB.

So one thing I might consider when architecting, is to have client kicking off a business process, the business process can then call the services for various application functionality. This way you can then 
  • Record and track the state of each processes.
  • Human task are considered as part of the process and can mix with system automation.
  • Having services built smaller, more modularize and easier to expend. 
  • Keep ESB clean, for that I am no business logic in the routes. 
  • Allow processes to talk to more protocol by taking advantages of Camel's smart endpoint. 
  • Hide transaction from process, since it is always complex when it's between departments, by having transaction within each service as boundaries will simply the steps.


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.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


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


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

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

My 2cents on the future of Integration - With Service Mesh/Istio and Serverless/KNative

It's been a year and half since I blogged about "Agile Integration architecture" (Gosh, time just flies). With the "microservices" and "cloud-native" hype, I was especially curious on how all these new concept and technology affect us on how to architect the integration systems. If you ever pay close attention to all the latest and greatest news from the Kubernetes community, I am sure you will hear a lot about the new "Service Mesh". And rumor has it that this is how integration can/should be done in cloud native world, but, is that so? Anyone who has ever worked on an integration project would tell you, it's a LOT more COMPLEX and can get worst overtime. I did a talk with Christian Posta in Red Hat Tech Exchange coming from a more comprehensive view of how different Red Hat technologies are applied under different patterns when building integration solutions. In fact he also did a great blog about it.

Since then, another topics has be…