Adjust Carbon Topology to Match High Availability Scenario Requirements - Wednesday, Novermber 28, 2012

  • By Kushlani De Silva
  • 28 Nov, 2012

High availability is a core enterprise requirement in any modern deployment. This ensures that systems can continue to function correctly even when there are failures. Ideally such systems should continue to function correctly and provide services while there are several failures.

Another important aspect is that system deployment architectures should ensure there are no single points of failure. Redundancy is the most widely used technique in designing such fault tolerant systems. This includes data redundancy, information redundancy, time redundancy etc. However, redundancy always comes at a cost and hence there is a cost vs. availability trade-off. Certain availability techniques may also result in performance overheads.

In this webinar, Afkham Azeez, Director of Architecture, will take a look at how these techniques are employed in the WSO2 platform to achieve high availability and fault tolerance, while taking the cost and performance factors into consideration. We will also look at some key aspects which will enable enterprise architects to make deployment topology decisions based on availability requirements at an optimum cost.

Afkham Azeez Director, Architecture Afkham Azeez joined WSO2 in December 2005, and he has served as director of architecture since 2011. In this role, he drives efforts focused on the development and enhancement of WSO2 middleware. Azeez is an elected member of the Apache Software Foundation and also a Project Management Committee member and long-time committer for a number of projects. He specializes in distributed computing, highly available and scalable applications, Java 2 Platform Enterprise Edition (J2EE) technologies, and service-oriented architecture.