Skip to main content


24 Lessons Learnt in the 12 Years at WSO2

I joined WSO2 in the second week after its inception on September 1 st , 2005. Since then I have been playing various roles. It has been a long journey, with interesting experiences. It has never been a smooth ride, but a very vivid and enjoyable one.  There were good times, not so good times, tough times and exciting times. But I have enjoyed it all the way along, and the journey and the outcomes so far have been exciting. I have been privileged to be here for this long.  And I have learned so many lessons thought-out. Here are the highlights, the top 24 from those many lessons I learnt. 1. Delegation is the first lesson to learn towards great leadership I am a geeky technical person. I can do many things on my own. When I started with WSO2 I joined as a C/C++ person in an architect role. I worked with the C team and created the Apache Axis2 C project. I would work hours, considered any issue that the code base ran into and worked on everything and anything that I
Recent posts

Ballerina Lang. Why New? Why Now?

Last Month, WSO2 announced the new language it designed for enabling integration, the flexible, powerful and beautiful Ballerina Language . ESB is Dead? Why a whole new language for integration. What is wrong with all the tools that we already have? The tools that we have, including the proven, stable and powerful WSO2 ESB is configuration driven. Uses mostly XML or something similar for configuration. Tough we call it configuration, for complex integration scenarios it can get really complex. Configuration over code does not scale.  In addition , every ESB is based on data flow architecture, and that does not scale either. The model is not good when it comes to complex scenarios. So we need a language, because it better scales for complex problems.  Scripting languages such as JavaScript are great.  Even Java and C# has lots of formidable alternatives and options. And why not use those?  In fact people do use them. And with the advent of micro services

Thoughts on Life – 2

I called this post a second, as I already had a previous one on life . People are good with stereotyping. They often think I am a Buddhist. I often wonder what that means to be called a Buddhist. If that means that I am born to a couple of Buddhist parents, you are wrong, I was born a Catholic. Being a Catholic child, I wanted to learn and understand. So as a kid I started reading the bible. That was what a good Catholic supposed to do. But actually, not many did even those days 25 to 30 years ago, So many years ago, when I started reading, I first read the preface of the book. It said, this book, that is the bible, would help you understand who you are and why you are here on this earth. To this day, I can still remember those words very clearly. So, that is what I am still doing. I seek to understand who I am and why I am here. I do not go to church much or pray much. So, the Catholics do not consider me to be a good one of them. However, in my understanding t

Cloud IDEs

Cloud is evolving. Cloud IDEs are the “next” big thing. They are quite interesting given the novel approaches that they bring to the software development arena. Some of the advantages they bring about include   Code available from anywhere   Simple code sharing Central code quality and best practices governance   Next level of continuous integration and continuous build Team dynamics While it looks that there is nothing like the native desktop to implement software using an IDE, the collaboration angle that is made possible by cloud IDEs are quite revolutionary.

Apache Stratos - The best PaaS to use

Apache Stratos (Incubating) is the Platform as a Service (PaaS) project from Apache community. WSO2 donated its cloud PaaS project to Apache, and it evolved over time with the nurturing from the Apache community in incubation. What is Unique about Stratos? As a PaaS framework, there are some key elements that the cloud computing industry is taking interest on Apache Stratos (incubating). The Tenancy Model Stratos uses an in-container multi-tenancy (MT) model. This means, for example, within an application server MT is available for applications. In other words, a container can host multiple tenants. This tenancy model maximizes resource utilization across all tenants. A single instance of a container can cater for multiple tenants. This model also yields a very good multi-tenancy density. There is no need to allocate memory (or other resources) per tenant. Auto Scaling The auto scaling model supported by Apache Stratos (Incubating) provides better control ove

Apache Stratos Architecture - Key Differentiators in PaaS Space

The unique and state of the art Apache Stratos ( Incubating ) architecture makes the platform as a service (PaaS) framework stand out among the rest. There are few factors that one should pay attention to, in order to understand the key advantages of the Stratos PaaS. Those include: Cartridge model Unified communication infrastructure Centralised logging and monitoring IaaS plugin capabilities Load balancer plugin capabilities Health check tooling plugin capabilities Cartridge Model Cartridge model makes Stratos unique among the PaaS alternatives because it allows the runtime extensibility of the PaaS framework. It is the enabler of the polyglot aspect of the PaaS container framework. The polyglot nature enables the support of multiple types of cartridges such as data cartridge, language cartridge, framework cartridges and operating system cartridges to be plugged in and managed by the PaaS framework in unified manner. Another key advantage of Stratos ca