This Kong Summit 2020 session focuses on the war stories, and subsequently the patterns HyperCurrent employed, from building an API chargeback/monetization product using OAS, Kotlin, Spring Boot and Kong. We will discuss how a programmatic approach can be used to deliver an elegant REST-ful API while enforcing an anti-corruption layer for domain logic without writing API contracts by hand. By using Kotlin and Spring Boot along with a controller/DTO approach, we can automatically produce an OAS contract, HTML docs, a console and a client side SDK.

In this session, we will explain the various communication design patterns for microservices running at scale.

During the early days of finding product-market fit, clouds were small. Often, we start with an EC2 instance here, a managed service there, then some Docker containers, microservices, and wait, Kubernetes! As clouds grow with the teams that maintain them, stable relics and legacy systems remain in production. The effort first goes towards building the future and satisfying clients — they’re paying!

Continuing on the journey of building a new API platform, NAB’s primary focus this year has been improving API quality by building tooling for API design and API governance. This Kong Summit 2020 session will cover NAB’s new API search capability, which allows quick API discovery across the organization, and how the team implemented decentralized API governance.

Microservices is a technology that is leading the march toward digital transformation in the world of application development. As the number of APIs increase, the need for a single entry point into the system becomes necessary. This means that a secured, robust, agile API gateway is highly important. However, what we often forget is that the API deployments must also move up with the CI/CD model, along with other components of the project.

Are you an enterprise architect who is currently facing the challenge to secure and observe service connectivity across every cloud and every cluster, including hybrid Kubernetes and VM environments? Kong Mesh, built on top of CNCF’s Kuma and Envoy, is a universal service mesh delivering simplicity and scalability to every application.

Organizations that embrace GitOps are able to develop and automate their end-to-end software development lifecycle by combining the power of Git, CI/CD and Kubernetes. However the path to get there can be rocky: operating in a multi-cloud environment, working with hybrid microservice and monolith APIs, helping teams discover and publish APIs to use, and moving legacy services to Kubernetes pose no shortage of organizational and technical challenges.

With the universal adoption of Kubernetes across cloud and data center platforms, organizations now enjoy a level of consistency across heterogenous infrastructure like never before. This opens up interesting challenges and opportunities for application deployment and IT operations. In this talk, we will discuss how organizations deploy Kubernetes across cloud, data center, branch offices and the edge. We will also cover how organizations can build a universal computing platform across multiple Kubernetes clusters running on heterogenous infrastructure. As a result, they get unprecedent application portability, deployment agility, security and control.

Are you an enterprise architect who is currently facing the challenge to secure and observe service connectivity across every cloud and every cluster? Kong Mesh, built on top of CNCF’s Kuma and Envoy, is a universal service mesh tailored to the enterprise architect that must provide modern and secure connectivity to the applications that the teams are building.

You want to migrate your existing application to serverless — and you don’t know where to start. This is a common problem that a lot of architects, CTOs and developers have, as it is very rare that we start as a greenfield project.