Skip to main content

Red Hat JBoss Fuse - Comparing different ways of Developing Fuse Application

Apache Camel in JBoss Fuse allow you to choose your favorite way to develop your integration application, and now it let you choose your favorite container to run it in. I put up a summary list of what each DSL are available, and made comparison between them. 

Available DSL in different Containers

Domain Specific Language
Apache Karaf in JBoss Fuse
(OSGi Container)

Blueprint DSL (recommended)
Java DSL
Spring DSL
JBoss Enterprise Application Server
(JavaEE application Server)
Java DSL with CDI (recommended)
DSL with JNDI registry
Spring DSL

The reason to recommend blueprint in Karaf is that it provides a dependency injection framework in OSGi. The service lifecycle are monitored and managed, as it can dynamically shutdown or activate at anytime, blueprint can performs actions based on the state of each bundle, it is a much managed way to do in OSGi Container.
In Java EE container, JBoss Enterprise Application Platform, it also has a dependency injection framework – CDI. As the container will take care of the lifecycle of the beans.

There are no right and wrongs of which DSL you choose to work with, in fact you don’t have to choose just one, the beauty of JBoss Fuse is the freedom that it gives you to do what you prefer to do. Just make sure you choose the ones that you are most comfortable with. With that in mind, since I have posted the three different ways to develop Integration application on JBoss EAP, I have put together a small table that compares the difference between them.

Comparing Application development using different DSL on JBoss EAP 

Java DSL with CDI
Spring DSL
Route XML with JNDI Registry
CDI context managed by container
Application Context as Registry
JNDI Registry
Bean Register
CDI API using annotation
On xml
Implement CamelContextLifecycle <JndiRegistry>, initiate and bind bean in JNDI registry
Required Web.xml setting
Setup JndiCamelServletContextListener
Camel Context and Route Building
Implement RouteBuilder Class
Spring Framework XML with naming *-camel-context.xml
Route Framework and in web.xml set routeBuilder-MyRoute context parameter
DataSource Lookup
Lookup by CDI and provide via @Producer
Lookup using jee schema in Spring
Calling JNDI name in component

JBDS Tooling
Route Description language

These are base on one fact that the JBoss Fuse subsystem is correctly installed in JBoss EAP.


Zachariah Young said…
What about using Spring Boot to run camel routes?

Popular posts from this blog

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 。

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 …

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 …