Lessons Learned Migrating an Existing Product to a Multi Tenant Cloud Native Environment

Moving to a Cloud Native architecture took changes in culture, processes and technologies. Teams collaborate with a DevOps philosophy and a "you build it, you run it" approach, providing teams with freedom. Most services are now written in Java, Javascript or Go, depending on each service.

Functionality that was previously running as part of the application was decomposed and reimplemented as Cloud Native services. The need to scale triggered a microservice architecture to support the existing app, and to scale the development organization. This drove the creation of API first services, Kubernetes operators, connections to external cloud services,... that work together to provide the full product. The multi tenancy aspects require considering the isolation between tenants, at multiple levels of the stack as well as resource consumption.

We will dig into specific details that require more attention when migrating to a Cloud Native environment, like resource management, decomposition of services or availability amongst others.