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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …