Skip to main content

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

This post is part of short session I spoke in Japan, strictly my opinion.

Red Hat JBoss xPaaS can help enterprise to adopt DEVOPS in many ways. My thoughts of DEVOPS, as in many years in the industry, I believe DEVOPS can be broken down to 3 major part. 
  • Self Service
  • Automation 
  • Continuous Delivery
I put self service first is because I think without achieving this the whole DEVOPS is just adding more work to both developers and operations, don't forget, the whole idea of DEVOPS is to reduce conflict between then and to be more productive when delivering softwares. 

"Without self service operation, cloud is just a Just expensive hosting" I love this phrase, found it when I was reading from Damon Edwards, Operation department is the past few years has focus on IaaS "Infrastructure as a Service", so they would have the flexibility to manage the network, have entire storage work as a pool to service and computing power can be distributed as needed. This is important in the way that now operation have much easier control to their hardware resources, but at the end what these resource is really used for is to provide software service to end users, these users can be either real customers, or just an application calling API. Developer must deploy their software to make it happen. 

So here is the case, operation still needs to install the container, middleware or any software is needed , configure everything, such as where the database, message broker is at, clustering for high availability and deploy the packaged and build software to the container. Red Hat JBoss xPaaS gives you a standard uniform way to allow developers to create the containers and have the based software, middleware or container installed. The standardization in the enterprise is important, because you do not want to give too much freedom to developer on the various versions and type of software to install, that would just add too much complication when it comes to patching and maintaining. Only the authorized platform running on enterprise cloud instead of any random one the developer downloaded from the internet. Also because of the standardized environment, DEV and OPS can speak in the same language, with easier to communicate.

But at the same time we also want developer to have the full power to create, configure and control the, at the end of the time, developers are the person most familiar with the application they want to push out. In Red Hat JBoss xPaaS, allows developer to select from varieties of standardized cartridges. Cartridges are like the template of different platform, from this cartridge, it will create a real running container with the specified template installed. The enterprise can even customize it's own cartridges. With this freedom to create their own application instance, developer no longer have to wait forever for deployment and can make configuration changes as fast as possible. 

The resource allocate to each container can be monitor and changed, those container that were not always needed, such as the testing environment, these resource can then re-allocated to others needed more. And depending on what platform you are using, with xPaaS it is very common and easy add an load balancer in front of the application allowing it to become scalable. 

And with Red Hat JBoss xPaaS developer can now focus on delivering their application on the cloud, there are many ways developer can do this through Red Hat JBoss xPaaS. 
  • Accelerating you application on the cloud - aPaaS
  • Integrate anything anywhere on the cloud - iPaaS
  • Moving Business process and core business application on the cloud - bpmPaaS
more to come next post about what is in Red Hat JBoss xPaaS. 

When xPaaS meets DEVOPS series:
Part One 
Part Two


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 …