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

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

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 …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …