Skip to main content

Fuse Integration Service - Auto Dealership Management Demo, Part Six

This series of blog is based on building an auto dealership management system on Fuse Integration Service. We will be creating three major functions in the system.
  • Sales report tracking 
  • Vehicle inventory status
  • Customer IoT Service
We have exported a sales report to a web page, provide current inventory status of available cars through web service. And collect customer data from IoT devices on their car then alert close by shops. 

In this part of the series, I want to look at Blue Green Deployment, and how Fuse Integration does it? So what exactly is this "blue green deployment" ? This is one technique to ensure the high availability and is very important in DEVOPS. In continuous delivery to ensure quality of the application, often we want to carry out a set of test before it goes on to an environment before releasing it to clients, this technique allow two versions of application running at the same time, so you can switch between the existing and update application. This will allow you to have near zero downtime deployments, in case of something goes wrong, we can quickly rollback to previous version with near zero downtime as well.

In Fuse Integration Service, because it's base on OpenShift, we can achieve blue green deployment through the Router capability in OpenShift. An OpenShift route expose services we create and mapping it to externally-reachable hostname. The Routers support the following protocols:
  • HTTP
  • HTTPS (with SNI)
  • WebSockets
  • TLS with SNI
From our demo, you can see each one of our service is mapped to a route.


What we are going to do is to deploy new version of our sales report service, without affecting the other one, and then switch this route to new version.

If you still remember the inventory project, it provides a json format list of sales summary

We want to remove the Date column, how do we make sure the data are correct before we deliver this application to all client? Simple, first, let's do the remove of the content in the code,  under our OpportunityGenerator java file,


And before we publish our updated application to OpenShift, we are going to make a little change, change the name of our project, in our pom.xml, change to another name of the application.


And then we can start publish it to OpenShift, with

  • mvn -Pf8-local-deploy

On the console, we will see sales report application running, with two different service name


  • salesreportfile-v2
  • salesreportfile

and if you take a look at the Route view, we can that now each service is connected to their own host name.

We can access the function with two different url from client,

  • http://salesreportfile-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking
  • http://salesreportfile-v2-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking

Now, for old clients they would access the application with the old route, now, for blue green deployment, we can simply switch the route that was originally point to service salesreport to the update salesreport-v2.  To do that, please go to a command line console, and login with the OpenShift v3 client.


ChristinatekiMacBook-Air:Desktop christina$ oc login
Authentication required for https://10.1.2.2:8443 (openshift)
Username: clin@redhat.com
Password: 
Login successful.

Using project "demo".
do a display of routes, again, to see what are available, 

ChristinatekiMacBook-Air:Desktop christina$ oc get route
NAME                 HOST/PORT                                     PATH      SERVICE              LABELS    INSECURE POLICY   TLS TERMINATION
dealeralert          dealeralert-demo.cdk.10.1.2.2.xip.io                    dealeralert                                      
gpsservice           gpsservice-demo.cdk.10.1.2.2.xip.io                     gpsservice                                       
inventoryservice     inventoryservice-demo.cdk.10.1.2.2.xip.io               inventoryservice                                 
salesreportfile      salesreportfile-demo.cdk.10.1.2.2.xip.io                salesreportfile                                  
salesreportfile-v2   salesreportfile-v2-demo.cdk.10.1.2.2.xip.io             salesreportfile-v2                               
Re-route the old service to another route,  
ChristinatekiMacBook-Air:Desktop christina$ oc edit route salesreportfile
Edit cancelled, no changes made.

You will be prompt with a file, edit the host name to the a new one, and save. 


Start re-route the hostname to our new service salesreportfile-v2
ChristinatekiMacBook-Air:Desktop christina$ oc edit route salesreportfile-v2
Edit cancelled, no changes made.

You will be prompt with a file, edit the host name to the original one we had, and save. 






Refresh your the console, and you can see now the original route is now pointed to the new application. 

Try access the content with
  • http://salesreportfile-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking
  • http://salesreportfile-old-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking
And that's it! Simple!

Comments

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 Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

The rise of Agile Integration, Integration is not DEAD nor LAME!

I wanted to blog about this for a very long time, but because of work and being too lazy to turn on my laptop on the weekends, now I finally have a couple of hours to sit down and start blogging.

"Integration is DEAD."
"No, no, let's talk about microservice!!"
"What is that again? Integration, you mean SOA? It's lame... ".

These makes the majority of the percentage when I talk about Integration. In fact, if you happen to be in any the software conference, you see the rooms full when it's about "container" and "microservice." I understand the nature of a developer, always seeking for the latest and greatest technology out there. BUT!! In my opinion, I don't think Integration is going AWAY if you containerize your application. Neither does it will DISAPPEAR in a microservice architecture. In fact, Integration just gets more complicated and tricky when you try to break an application into smaller pieces and have them runni…