Skip to main content

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

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

The last part of my talk is about continuous delivery. The idea of this is to make enterprise more lean,
and react more responsively from user feedback. We all try to find ways to make our application more agile. The way I see many enterprise are still doing especially in my region is they tend to have a rather "Large" release. Each release contains too many updates and new functions. Due to the facts that enterprise wants to have more stable releases, so they have a tendency of having a fully tested large bundle of application to deploy. The process normally takes weeks, by the time software reaches the end users might be too late, and feedback and response to the application from user has to wait weeks. For developer, it's painful to handle all the different versions, and QAs needs to test a large set of functionalities. If anything goes wrong in production, to rollback to previous version will cost enterprise a fortune, because all the available services now needs to shutdown due to one single problem.


On Red Hat JBoss xPaaS, with a little help from Jenkins it is really easy to achieve continuous delivery. This is how it's done, when developer finished developing their application, they first push
their application to an source control repository, in this case we are using git, then a pre-installed Jenkins server on Red Hat OpenShift (PaaS) will pick up the change, start building the application with maven plugins, and then it will run through a series of automatic test, when there are problems, it'll automatically send a test report to the developer, so the developer gets the instant feedback on their application. When the application pass the automatic tests, Jenkins will automatically spin up a container with the middleware it needs and the newly developed application. There is a Jenkins plugin you can utilized, so it saves you lots of scripting work. Then another set of testing will be done before it reaches the UAT, the same applies to UAT, after it passed the test in testing environment, it'll deploy the application to the newly created UAT containers. This is where the QA comes in, does testing and then signal Jenkins to spin up Production container and ready to provide service in Production.

This new continuous delivery, can shorten the lifecycle so it can adapt and response to user feedback in much quicker way, and react faster to market shift and also aline with most current business strategy. And because each build has less amount of changes and updates, it's much easier to rollback and it'll have less impact to the business.

That's all I have gone through in my talk, in summary, Red Hat JBoss xPaaS provides an unify entry point for DEVOPS, so both DEV and OPS speak the same language and let enterprise standardize the development and operation environment. With continuous development, now enterprise can be more agile and flexible to bring business idea into action much faster. It also improve productivity and most importantly, resolve the conflict between DEV and OPS.

Comments

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

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

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

prefill

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

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

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …