Skip to main content

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

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

Automation plays an essential role in DEVOPS, the entire cycle will cripple without automation, the whole idea of DEVOPS is to speed up the process inside enterprise, and relief developer and operation from day to day repetitively meaningless routines. Automation meaning that anything the machine can do, make the machine do it. In the old day, due to technology limitation, politics or if it's just simply not having time to do it, there are many jobs that needs to have human involve. If you seriously want to introduce DEVOPS, You will find that you spend majority of time dealing with automations.

There are few aspect in Automation in the DEVOPS lifecycle, let's take a look at my real life experience, it's one of the most anti-automation case I have ever seen in many years of my consulting career. This happens in one of the SI company, where they were responsible for maintaining a banking solution for a bank, due to many reason, their project has failed to deliver the full function on time, so their project manager decided to move the current version to production first as phase one, then deliver the rest of the services later when it's ready. It was a large monolith application, the developer in the project will push out a version of the application, then a quality assurance personnel will come in and test that version of the application, the scope of the application was huge, plus the new function, it take a day or 2 for the QA to test and return the feedback to the developers. By the time the developer receives the feedback, he/she has already pushed out 2 more version, now he has to go back to the problematic version, and fix it, for me as a developer, I hate being interrupt in the middle of something, and go back to the code 2 week before and try to remember, pick up and fix bug. It's not the problem of fixing the bug, if the feed back could of given to developer right after the code to is out, it'll save a lot of time from all these recaps. This process has taken 2 weeks in the QA cycle before it is pushed to production. The operation then take the application, create an pre-production environment, and then it is tested again, of course by human again. A normal function for this bank will normally take about a month.

This is an extreme case, and I see many improvements can be done, but most importantly, eliminating the human testing routines and should be the top priority. To help speed up the automatic testing, in Red Hat JBoss xPaaS, you can setup an CI server such as Jenkins, that detect from our version control repo, which is built-in in xPaaS using Git. So when everything there is a push to the git, the CI server can detect it, then automatically create an production like container to hold the application, then it can automatically deploy and test the current version. Of course, to make the automation of testing easier, one might also want to consider breaking down applications into smaller pieces, and have these smaller pieces deploy on separate container, this makes testing unit simple and quick. Because of the nature in xPaaS, it is very easy for xPaaS to quickly spin up a container, without heavy involvement of developer and operations. Allowing this will make the whole architecture to become more agile and more flexible.

Normally automating these processes are difficult, because you will need to take in account on different version, software, networks and other environment factors. That makes automation complex, Red Hat JBoss xPaaS has a range of middleware already built-in so there is no need to care about the installation script, that make the entire automation much quicker and easier to maintain.
That's all for automation, next time it's the last part of the series, Continuous Delivery.


Popular posts from this blog

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 …

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 …