WSO2 Business Activity Monitor (BAM) 2.0 - a new beginning - Thursday, 2nd February 2012
By Dasunpriya Anuradha Mallikarachchi
- 21 Dec, 2011
Monitoring business activities in a service oriented architecture (SOA) translates into monitoring relevant web services. This means that capturing messages and statistics from servers deployed in the SOA deployment should be trivial to monitor and gain an insight into what happens in an organization.
Though this is the case, a monitoring solution needs to wary of other factors that get involved in serious monitoring use cases:
- Customization - Different groups within an organization will have different requirements, thereby requiring to define different key performance indicators. (KPIs).
- Robustness - Monitoring should have virtually zero impact on the servers which are monitored, and should be able to handle any failure gracefully.
- Performance - Colossal loads passing through SOA deployments is quite common, and the monitoring solution should be able to handle same.
- Scalability - It should be scalable in multiple senses, by message load, by data volume, by processing volume etc.
WSO2 BAM 2.0 is a complete re-write of the BAM 1.x version, based on lessons learnt in order to suit the requirements stated above. This session will discuss how we address these requirements based on NoSQL data storage, super fast data transfer rates, configuration based analytics and WYSIWIG UI development tools.
Tharindu, Product Manager of BAM and Senior Software Engineer, has been involved in Web Service technologies for 3 years. He has practical experience working with projects like Apache Cassandra, Apache Hadoop, Apache Thrift and various other open source projects. He has been involved in many development projects in various countries in Europe, Asia and the Americas.