Skip to main content

JBoss Fuse - Easy Load Balancing Web Service with JBoss Fuse

There are few ways to do load balance with web Service, using the Http Gateway is probably the easiest way to do the load balance in Fuse,

First we deploy our restful webservice bundle to 2 containers in Fuse,











by doing so, we have 2 container running the web service on 2 different container with different IP:Port combination.


But, inside your application container, make sure you expose your web service to the fabric. Please see the tips and trick post I post before to see how it is done.

The reason we are doing this, is to register our web service, in this case a restful webservice, is to let fabric know there is a registered service, and know where they are.

Next, we are going to add a http gateway to a container, it will handle all the request dispatching, for load balance, this http gateway will find all the registered service under /servlet and /webapp. Also open up a port for client to connect. 

Create a new container, and add Gateway/http profile to it. 









By default, the http gateway service will provide in port 9000, you can alway change it by changing the port properties inside io.fabric8.gateway.http.properties of Gateway/http profile.


And the default load balance behavior is round-robin, but there are 3 kinds of option you can change to,

  • round-robin
  • random 
  • sticky

and change it by configuring the "FABRIC8HTTPGATEWAY_SERVICE_LOAD_BALANCER" properties inside io.fabric8.gateway.http.properties of Gateway/http profile.

And that's it! Can't believe how easy it was!

So to see it running,
here are both of my services, through the API page, you can see they are both running on different container,






With the http gateway, now I can access the restful service through the gateway.



Thanks, Let me know you feedback.

Comments

游宗霖 said…
How can we make http gateway itself high availability? In our architecture we use two haproxy and keepalived and one VIP which is bind by keepalived service. So our client need only to call one ip. Is the same architecture fit for http gateway?
I believe you are looking for something like this: http://wei-meilin.blogspot.com.br/2014/09/jboss-fuse-how-to-setup-cluster-of.html

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

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

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

prefill

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

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

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…

The rise of Agile Integration, Integration is not DEAD nor LAME!

I wanted to blog about this for a very long time, but because of work and being too lazy to turn on my laptop on the weekends, now I finally have a couple of hours to sit down and start blogging.

"Integration is DEAD."
"No, no, let's talk about microservice!!"
"What is that again? Integration, you mean SOA? It's lame... ".

These makes the majority of the percentage when I talk about Integration. In fact, if you happen to be in any the software conference, you see the rooms full when it's about "container" and "microservice." I understand the nature of a developer, always seeking for the latest and greatest technology out there. BUT!! In my opinion, I don't think Integration is going AWAY if you containerize your application. Neither does it will DISAPPEAR in a microservice architecture. In fact, Integration just gets more complicated and tricky when you try to break an application into smaller pieces and have them runni…