Skip to main content

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

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

Red Hat JBoss xPaaS allows enterprise to deploy their application both on premise and cloud. Inside this hybrid environment developer does not need to worry about that sort of container or deployment environment it is deploy on. So developer can easily build their application, integrating with other service across enterprise or cloud and even orchestrate business process and rules.  That means developer can now expose their service to the outside world, it can be either through web service, either it's SOAP with XML or Restful API with JSON content. They can take their core business rules in the rule repository and expose without the needs to wrap them in a servlet, orchestrate outside service or provide an endpoint to start up an processes on the cloud. And because the growth of handheld device, the ability to talk to the "internet of things" suddenly becomes one of the hottest topic, Red Hat JBoss xPaaS, allows devices to communicate through various protocol such as AMQP, STOMP or MQTT.

There are several choice in xPaaS for developer to choose from, and find the best suited middleware to run their application on.

aPaaS, JBoss EAP for xPaaS, This provides an application container service, in aPaaS, you have JBoss Enterprise Application platform as the middleware, this maybe the fastest stepping stone for an enterprise with traditional application architecture to move their service on the cloud. Because JBoss EAP is an full JavaEE certified application server, that means, developer can simply deploy their good old JavaEE application to this environment, and it should just work. After deployment, if the there is a need to scale up and down the application, we can easily create more instance of the application, achieve load balancing by creating an HA PROXY provided in aPaaS in-front of the applications, that will automatically share the load. JBoss EAP comes with cluster ability, combination of HA PROXY, we can now make sure the data are never lost and can achieve zero downtime.

iPaaS, JBoss Fuse for xPaaS, This Integration Services allow developers to connect services, send and receive messages between them. As increasingly number of service are available through cloud, many enterprise wants to take advantages of these service, but connecting to these services could mean developer needs spend time to code and maintain application just to connect them. There are 150 more built-in connector in iPaaS, so developer can take advantage of these components without connectivity code but just configurations. Connecting service are complex, because often you need some sort of routing or filtering, iPaaS with JBoss Fuse as the middleware, by using the builtin Enterprise Integration Pattern in Camel, developer can effortlessly drag and drop connectivity logic using Tools provided. The messages formate from these service can come in many form, iPaaS can also transform these data to developer's desire format. Such as from XML to POJO, CSV to JSON.. Lastly we can now take the message broker up to the cloud, other then the wide variety of protocol it can use, best thing is that developer can use it as a buffer storage space to prevent messages flooding from the internet!

bmpPaaS,  JBoss BPM Suite for xPaaS, is the recent member to join Red Hat JBoss xPaaS family, normally Business rules are protected within the enterprise, and using JBoss BRMS or JBoss BPM suite, developer can stop hard coding "if...else, while..." in their application, all the business rules are kept and maintained in a repository, so it can be centralized managed. When developer need this particular rule, all they have to do is to kickstart this rule and enter object with data in, the rule engine will process the data using the rule and then return the result to developer. bmpPaaS allow developer to take this business rule processing to the cloud. Also inside a large enterprise there must be many business process the needs to go through other departments, it could be automatically processed by machine or it needs human care, we know have the automatic endpoint allowing these process to be kickstarted on the cloud too!

So here are some of cool PaaS services offer by Red Hat JBoss xPaaS, this can save developer tons of effort when developing application on the cloud.

Next part we will continue on discuss about automation with Red Hat JBoss xPaaS.

When xPaaS meets DEVOPS series:
Part One 
Part Two
Part Three

Comments

Nasreen Basu said…
excellent piece of information, and let me tell you, your site gives the best and the most interesting information. This is just the kind of information that i had been looking for, i'm already your rss reader now and i would regularly watch out for the new posts, once again hats off to you! Thanx a lot once again, Regards, devops training in hyderabad,<

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 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 …