Skip to main content

Red Hat JBoss xPaaS - When xPaaS meets DEVOPS - Part One

This is post is the content of one of the short session I spoked in Japan. and strictly just my opinion.

When I was a enterprise architect (long ago in Taiwan), I'm in-charge of several application in the company, we receive a large number of user requirements per month.  There were about 10 developers in my teams, every time we push out a release, we always deploy it on a testing environment. Depends on if we are busy, we often have many versions deployed on testing environment. But the process of going through to create one is really painful. The developer needs to wait few days for resource to create and properly configured. Worst is the amount of forms and estimation stats, configuration documentation the developers needs to fill in. And when the code has finally reaches the production, it's time for the operation team to worry. If, by any chance, something went wrong in the production, became operation's biggest nightmare. They need to figure out what was really happening, and try to resolve by calling developers, but we as the developer cannot alway fix the problem instantly without reproducing the problem.

The role of developer and operations are conflict by nature. The developer to create changes, and he/her job is to add or update new feature and function to the software, tried to be as agile as possible, so when ever they need to communicate with the operations, they get very frustrated as it seems to them, the operation team never have the courage to try anything new or even refuse to change. On the other-hands, operation thinks developers are irresponsible, they can never deliver a software that is 100% stable, their responsibility are to make sure the system is 24-7 online or at least  99.999999% of uptime, they are also responsible to enhance the service level, for that the way operation does their job needs to be static. The fight between two parties is going to result a tremendous drawback and hurt company at the end. (I have hold or participated in countless meetings just to resolve the problems between two teams, trust me, it's very painful..)

So when the concept of DEVOPS emerges, I though it brought a ray of light to this dark, but actually introducing it into the enterprise is surely very difficult. However, Red Hat JBoss xPaaS makes the perfect solution when it comes to DEVOPS.

My understanding of DEVOPS can be broken down into 3 main areas,

  • Self Service
  • Automation
  • Continuous Delivery 

I would like to talk a little about how Red Hat JBoss xPaaS help in these 3 Areas base from my understanding of the technology.

When xPaaS meets DEVOPS series:
Part One 
Part Two


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…