WSO2 at APIdays Singapore

API management was introduced because of the needs of decentralized ownership of web services. During the time where service-oriented architecture (SOA) was popular, one of the main requirements was to expose a web service in a centrally governed way. That is how API management came into the picture. However modern application development practices mandate a more decentralized approach in order to improve productivity and agility by giving teams more autonomy to self-serve. In addition to that, microservice philosophy also favors decentralization in all aspects of software design. Considering all these API management also needs to move towards decentralized architecture. Decentralization is really about people, not technology. At a high level, it is about giving the business greater agility when bringing new ideas to market.

In this talk, we will discuss about how to move towards decentralized API management. We will explore the following topics:

• Centralized API management.
• Composing microservices to APIs
• Decentralized software lifecycle management for APIs
• Decentralized infrastructure challenges

With the emergence of microservice architecture (MSA), software architects and developers are increasingly adopting microservices for faster innovation. Smaller teams, agile software development life cycles, freedom to use heterogeneous technologies, and early feedback cycles are the key drivers for its success. But MSA comes with its own challenges. Because of this disaggregation of architectures, the number of endpoints is exploding. Communication among these endpoints will be a key challenge. To address this, software architects came up with a very promising, future proof software architecture known as a Service Mesh.

Multiple implementations of Service Meshes exist, however none of them have been able to address the concern on how APIs can be exposed in a controlled and secure manner to its API consumers. WSO2 API Manager provides out of the box integration with Isitio Service Mesh, which allows one or more APIs from Isitio mesh to be exposed for consumption via the API Manager.

In this session, we will explain how services meshes and API management can co-exist. We will also draw references to WSO2 API Manager and how it can be used with Isitio to manage APIs that are exposed for consumption.

Singapore is leading the open banking revolution in Asia. Although non-regulated, the Monetary Singapore Authority (MSA) fully support banks opening up their APIs to third-party providers. This favourable environment coupled with banks’ identifying open banking as a driver of competitive advantage has led to open banking adoption as far back as 2016.

So what’s next for open banking in Singapore? Will more banks continue to open up their APIs and move closer to digital banking? Will banks who have already opened up their APIs look at further leveraging the ecosystem of third-party providers to improve customer experiences. And where does technology fit in?

This session aims to share our experiences in global open banking and how banks leveraged technology to build API ecosystems that customers fall in love with. It will cover

• Open banking for regulated regions: Lessons learned from banks, big and small
• Open banking for non-regulated regions: Why technology is the make or break of success
• What to expect for open banking in the Asia Pacific
• One step closer to digital banking: The WSO2 vision for open banking

Implementing a successful open banking architecture is critical for a bank to fully leverage the benefits of open banking. Everyone from your compliance officer to your open banking project manager to your CTO needs to have complete confidence in the open banking platform you choose. Your open banking architecture plays a large role in determining how effectively you open up your APIs, provide a seamless third party experience and ultimately offer a better customer journey than that of your competitors

This session will cover:

• The key requirements for implementing an open banking architecture
• How regions across the globe have met these technology requirement
• How WSO2 Open Banking meets these technology requirements