Skip to main content

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

This is post is the content of one of the short session I spoked in Japan. and strictly just my opinion.

When I was a enterprise architect (long ago in Taiwan), I'm in-charge of several application in the company, we receive a large number of user requirements per month.  There were about 10 developers in my teams, every time we push out a release, we always deploy it on a testing environment. Depends on if we are busy, we often have many versions deployed on testing environment. But the process of going through to create one is really painful. The developer needs to wait few days for resource to create and properly configured. Worst is the amount of forms and estimation stats, configuration documentation the developers needs to fill in. And when the code has finally reaches the production, it's time for the operation team to worry. If, by any chance, something went wrong in the production, became operation's biggest nightmare. They need to figure out what was really happening, and try to resolve by calling developers, but we as the developer cannot alway fix the problem instantly without reproducing the problem.

The role of developer and operations are conflict by nature. The developer to create changes, and he/her job is to add or update new feature and function to the software, tried to be as agile as possible, so when ever they need to communicate with the operations, they get very frustrated as it seems to them, the operation team never have the courage to try anything new or even refuse to change. On the other-hands, operation thinks developers are irresponsible, they can never deliver a software that is 100% stable, their responsibility are to make sure the system is 24-7 online or at least  99.999999% of uptime, they are also responsible to enhance the service level, for that the way operation does their job needs to be static. The fight between two parties is going to result a tremendous drawback and hurt company at the end. (I have hold or participated in countless meetings just to resolve the problems between two teams, trust me, it's very painful..)

So when the concept of DEVOPS emerges, I though it brought a ray of light to this dark, but actually introducing it into the enterprise is surely very difficult. However, Red Hat JBoss xPaaS makes the perfect solution when it comes to DEVOPS.

My understanding of DEVOPS can be broken down into 3 main areas,

  • Self Service
  • Automation
  • Continuous Delivery 

I would like to talk a little about how Red Hat JBoss xPaaS help in these 3 Areas base from my understanding of the technology.

When xPaaS meets DEVOPS series:
Part One 
Part Two


Popular posts from this blog

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 …

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 …

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 …