Skip to main content

Red Hat JBoss A-MQ - A-MQ in Internet of Things, Sensor transmitting vital signal to Biomedical dashboard via AMQP

I was amazed by the increasing number of people mentioning "Internet of Things" in the recent conversations, if you already know what IoT is, please skip this part and go straight to my demo. :)

From Wiki,

"The term Internet of Things was proposed by Kevin Ashton in 1999,... it originally refers to uniquely identifiable objects and their virtual representations in an Internet-like structure. ...... Today however, the term Internet of Things is used to denote advanced connectivity of devices, systems and services that goes beyond the traditional machine-to-machine (M2M) and covers a variety of protocols, domains and applications."

From my understanding, is that more and more light weight, hand carry device or smart appliance are produce and manufactured. All these device works great on it's own, such as mobile phone,  TVs, GPS or even sphygmomanometers. But they work even better with the internet, by transmitting their live data, we were able to get better and quicker response and reaction. But the number of device out there is much greater then the current machines we are used to today. How do we cope with the vast amount of data floating in and make sure the data was delivered reliably?

The nature of messaging technology that allows information to deliver safely and reliably to the endpoint, has made it become the perfect medium to be the front line of IoT.

Under different circumstance, different ways and format to transmit information are used. So we can achieve better and more efficient performances.

STOMP (Streaming Text Oriented Messaging Protocol)
Purely text base protocol. And since it's in text format, almost every broker supports it. But being the whole text format,I wouldn't count on it's performance.

MQTT (MQ Telemetry Transport)
The most "light weight " Protoco out of all there. It is design for remote client with limited bandwidth to  deliver messages. MQTT has small code footprint. It's goal is simply deliver messages to the broker, the broker is then responsible to pass on the messages to other endpoints.

AMQP (Advanced Message Queuing Protocol)
Open standard application layer protocol, It mandates the behavior of the messaging provider and client to the extent that implementations from different vendors are truly interoperable. WIth A-MQ, you can always use this protocol by using JMS API with Apache QPid Project.

This demo showcase how the sensor transmit Body vital sign by sending signals via AMQP to A-MQ queue. And the information is catch by the consumer in the Dashboard (again with AMQP) then display the data on the web dashboard.

This video shows you how to install and run the demo:

Biomedical Dashboard demo from christina on Vimeo.


Irl Balcueva said…
This comment has been removed by the author.
Irl Balcueva said…
oday is the year of internet of things, this is the most commonly used today, everything from smartphone, cars, home. 2015 is a year of connected devices, home automation, connected cars. the big question for this right now is the security issues. Since cyber crime is always around the corner. Thank you for this very interesting info of yours. Hope you have time reading our blog.

Popular posts from this blog

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…

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.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


Connection Pool 最多可以開啓的 connection 數量


事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。

My 2cents on the future of Integration - With Service Mesh/Istio and Serverless/KNative

It's been a year and half since I blogged about "Agile Integration architecture" (Gosh, time just flies). With the "microservices" and "cloud-native" hype, I was especially curious on how all these new concept and technology affect us on how to architect the integration systems. If you ever pay close attention to all the latest and greatest news from the Kubernetes community, I am sure you will hear a lot about the new "Service Mesh". And rumor has it that this is how integration can/should be done in cloud native world, but, is that so? Anyone who has ever worked on an integration project would tell you, it's a LOT more COMPLEX and can get worst overtime. I did a talk with Christian Posta in Red Hat Tech Exchange coming from a more comprehensive view of how different Red Hat technologies are applied under different patterns when building integration solutions. In fact he also did a great blog about it.

Since then, another topics has be…