Get your ticket or log in to build your agenda.

PRO WORKSHOP (MICROSERVICES) : Automatic Microservices Observability With Ballerina

Anjana Fernando
WSO2, Director of Developer Relations

Anjana is a Director of Developer Relations at WSO2. He has built up the expertise in data analytics and enterprise integration by leading several products at WSO2. He has also helped numerous customers in implementing their integration strategies. His latest venture is his role in the Ballerina project, where he has been involved extensively in the design and implementation of the language and its runtime, and now primarily works on its ecosystem engineering and evangelism activities. Anjana presents frequently in events, such as DevOps Pro, ApacheCon, API World, WSO2Con, KubeCon, BallerinaCon, DeveloperWeek, and many tech meetups. He is also the author of the very first Ballerina book:

Modern applications are increasingly becoming more of a distributed computing problem. With the availability of feature rich cloud services, our solutions are increasingly relying on these in implementing functionality. Also, the application itself is adopting more of a disaggregated architecture in favor of extensibility, scalability, re-usability, and deployment flexibility. This is how microservices architectures are becoming popular everyday. But there is no free lunch; with the benefits, there are new challenges that are introduced. Compared to monoliths, with microservices we need to handle the complexities that come with networked architectures, such as communication latency, unreliable connections, protocols, data formats, and transactions. So while we come up with many new techniques to tackle these problems, it’s vital for us to have a proper observability functionality to verify the behavior. The Ballerina programming, which is designed from ground-up to work with networked applications, takes in a unique approach by having built-in observability functionality in language constructs. It exploits the language awareness for network operations, such as service types, remote function invocations, communication resiliency mechanisms, to automatically observe the operations done by the users. Basically the Ballerina platform takes care of the majority observability situations automatically, so the developer can only focus on the core business logic, and not sprinkle your code with lots of observability code. In this session, we will look at these features on how these built-in functionality will be used for metrics generation and distributed tracing using the Ballerina platform.