Asanka Abeysinghe

The number of microservices running in enterprises increases daily. As a result, service composition, governance, security, and observability are becoming a challenge to implement and incorporate. A “cell-based” architecture is an approach that can be applied to current or desired development and technologies to address these issues. This technology-neutral approach helps cloud-native dev teams become more efficient, act in a more self-organized manner, and speed overall release times. In this keynote, Asanka will introduce the "cell-based" reference architecture, which is API-centric, cloud-native and microservices-friendly. He will explain the role of APIs in the cell-based approach, as well as examine how real applications are built as cells. Asanka will explore the metrics and approaches that can be used to measure the effectiveness of the architecture and explore how organizations can implement the cell approach.

In today's experience economy, creating unique digital experiences has become a competitive advantage. However, delivering these experiences is challenging, and organizations often struggle to translate their strategies into value. Technology leaders frequently find themselves focusing on building internal developer platforms to reduce complexity and enhance productivity, rather than concentrating on digital innovation. This requires substantial investments in time, money, and specialized skill sets.
As a strategist or a craftsman embarking on a digital transformation journey, you might be pondering:
Why is having an internal developer platform crucial for success?
What are the characteristics of an effective internal developer platform in the context of the modern experience economy and cloud-native architecture?
How does an internal developer platform accelerate an organization's digital strategy and boost the efficacy of digital strategists?
In this session, Asanka will address thes

Agility is a common objective everyone defines as a high priority goal. But how many really achieve key results? Surveys have identified that the success rate is less than 10%. Even organizations that follow various agile methodologies do not operate in an agile way across the board; therefore, people call it an agile waterfall or wagile approach.
Is there a pragmatic solution for organizations to become true-agile?
Programmability - the ability to automate actions, procedures, processes, and runtimes you used in the entire application lifecycle giving us a path for success. Infrastructure automation is a common practice, but this approach is going way beyond that by having programmability from the cradle to the grave of an application.
By utilizing the power of programmability and having the end to end automation increase productivity, flexibility, decommission repeatable tasks, and provide more time to implement innovative ideas.

Middleware is essential for application development which increases the productivity of full-stack developers by bringing battle hardened functional capabilities covering the majority of a digital-driven project. However, with the adoption to Microservices and cloud-native application architecture middleware cannot use like used in the past, this is a solution for the above problem.
Complexity created by distributed computing encapsulated by the middleware for over two decades and made application developers productive by letting them focus on business logic relevant to their domain. Modern architecture and technology drift, such as Microservices, Cloud-native, and Serverless do not have room to embed middleware into the application development while the need is still there.
In this talk, Asanka is going to deep-dive into an API-centric, decentralized, and code-first approach to fill the void of middleware and make the application developer productive again.

Organizations are now using low-code and pro-code tools to build digital experiences internally and externally. However, not having the right alignment between these two approaches slows down delivery.
Different developer personas that work in silos, no connection between low-code and pro-code applications, low-code creating unmanageable shadow IT applications, no single codebase or build pipeline, and interruptions to the professional developer flow are some significant drawbacks.
In this session, Asanka will look at a platform approach to bridge the low-code and pro-code chasm.