Skip to main content

Red Hat JBoss - HP IT Summit in Taiwan, Openshift and Devops

Last Friday, I had a JBoss talk in HP taiwan IT summit, normally, developers doesn't really go to the forums like this, HP are know for their Hardware and infrastructure solutions, but I was there to break the boundary between developers and infrastructure gentlemen/ladies :)

It was a very short 40 minutes session, and it was the last session of the day, to make sure everyone is still awake and concentrating, I also did a little demo too.

As a developer, I wanted to discuss how Openshift has really boost the DevOps, and make our life much easier from a developer point of view, and also allowing system administrators to be relieved from their boring day to day routine job.

Automation place a big part of the DevOps world, OpenShift let developers create and setup a runtime environment on their own, so no more email or phone calls between 2 parties, developers can spin up an application server in few seconds without bothering his/her colleague. Inside Openshift, there are various cartridges you can choose from, the cartridges are how OpenShift installs Languages & Middleware, so there will be an JBoss Enterprise Application Server, or JBoss Fuse for developers to choose their middleware platform, and there are also cartridges of MongoDB or Postgresql and more, if developer needed a database. The instance developers create can be deploy both on premise or cloud, it is completely transparent to developers. They will not need to worry about anything can can then concentrated on their work. With JBoss developer studio it seamlessly combines with openshift, so developers can quickly update their code through the git to the repository inside their openshift nodes.

To make sure we make the most of DEVOPS, we should seriously consider breaking our code/project into smaller chunks, (Believe me, It is so common in Taiwan that I bumped into a WAR or EAP even a JAR file with 1-200 MB, even seen one with more then 700MB). Modulize it, It will improve the development cycle

1. Shorten the developement cycle with less code to maintain and test
2. Less complex code, so it's easier to maintain.
3. Modules can be reused. Even Test code are easier to create because we have limit what each module can do.
4. And be replace or remove with less impact, because it's less sticky in code.

To modulize it and make it more suitable to run in cloud, it is important that we keep it stateless. Or keep the state in your data. Openshift is also a great xPaaS, meaning it provides a great platfrom that integrates everything together with the help from JBoss Fuse technology. With the combination of JBoss Fuse and Openshift, it allows administrator to dynamically create as many instance as the hardware can handle. Give more flexibility to them.

I hope I crack a little hole in the wall between devlopers and system adminstrator with Openshift. :)
Thanks! And here are the slides on that day.


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 。

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…

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…