Skip to main content

JBoss Fuse - Fuse workshop 101 - Part Three

It's really difficult to design or architect an Integration project, especially within an Enterprise, there are so many factor to take into considerations.
  • System characteristic
  • Data mapping
  • Interface of systems
  • Risk management
  • Security 
  • And even office politics comes into play, I have to say this is the most time consuming and can quickly become nightmares be not deal carefully. 

This quickly became a headache for architects, and people constantly ask for best practice, I have to say, there are no single best practice, because it is not an ONE SIZE FIT ALL answers, integrating system is all about problem solving. 

So how do we solve an complex integration problem? YUP! you are right! break it down to smaller problem and then tackle them one by one! And fortunately this book "Enterprise Integration Patterns" by Gregor Hohpe has most of the solutions. This book "provides a consistent vocabulary and visual notation to describe large-scale integration solutions across many implementation technologies". 

To put it in my words, it's a collections of patterns, each pattern is to solve a design problem, so by implementing the patterns to the pieces of problem you have already broken down and put the patterns together will give you an idea of where to start from. Of course for every pattern it has it's pros and cons and many things to consider. That why using Camel as the tool that supports EIP will allow you to modify or refine your design with a few easy modification steps! 
For this workshop, we talk about Enterprise Integration Patterns, I will skip all the parts that talks about individual pattern, seriously, it's going to take too long, and there are so many resource on the internet that talks about them. I would recommend you visit the official EIP site to learn what each and every pattern does, and maybe read the book if you have time! It's really helpful. 

Let's look at this Ordering system. Shops from different location sending in order data, it needs to go into both inventory system to check for product availability and accounting system for finance check up. Then the inventory sends the product ready for shipment. At the same time it sends a confirmation email to the customer along with some advertisement and coupons. 


OK, so here is the problem, how do I make sure inventory and accounting system gets the message as soon as possible? what if there is something wrong with customer's payment? How do I make sure the shipments are shipped efficiently? And what about the notification system, how do I deliver it? 

Here are my thoughts on the solution, 
To make sure both inventory and accounting system receives the message at the same time, we will use the "publish and subscribe" pattern, so a copy of the message are send to all receivers. so the inventory and start the inventory check and the shipping process immediately and accounting system can start process it's finance and billing process.


If the payment ever goes wrong, a message will be send to a "invalid message channel", that will be pickup by the inventory system and cancel the shipment.  

The shipment message should be sorted according to different delivery priority and area to delivery and "aggregate" into a bigger chuck so it's easier for delivery truck to divide it's duty, and the content send to delivery system should be "filtered" so it only contains necessary data. As for notification, we also want to make sure we send it to the notification system at the same time, but send an cancelation letter or a successful letter in our "Recipient List". And as well as that, we will also "enrich" the content with coupon and the advertisement that might interest the customer. 


OK, what happen if the online shopping team comes in, and they would also like to do the same thing, but their ordering data comes in with a totally different format, so first, we will certainly reuse what we have ready done. (There is a fine line between reusing code and rewriting it all over, but here we assume the process behind is exactly the same). So by "transforming" the data the same as shops, then publish the content to the existing channel will certainly saves you lots of time!  


Slides for the workshop:

As for lab, continue from last one, this time we are going to separate the processing route for VIP and normal stock purchase. Also we want to introduce another vendor that trade with our system but with orders in one large file, we need to spilt the content before reusing our existing route! 


Lab Instructions:


Here are the other parts of the workshops!
Workshop part 1 - Camel basic and components
Workshop part 2 - Data Transformation 

Comments

This is a good article & good site.Thank you for sharing this article. It is help us following categorize:
healthcare, e commerce, programming, multi platform,inventory management, cloud-based solutions, it consulting, retail, manufacturing, CRM, technology means, digital supply chain management, Delivering high-quality service for your business applications,
Solutions for all Industries,packaged applications,business applications, Web services,
Business intelligence, Business Development, Software Development etc.


Our address:
2002 Timberloch Place, Suite 200
The Woodlands, TX 77380
281-364-1799

prologic-corp

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

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 …