SATURN 2020

When you design a system for the cloud there are certain characteristics that are important. Some of these characteristics are there from day one and some are added because of experiences encountered over time. Managing a live system sometimes leads to architectural decisions that are there to not only protect customers but to also protect the developers that work on these systems. Microservices-based architectures are great when your system is deployed on the cloud for a bunch of reasons. But what happens when you need to move your cloud-based architecture to an on-prem system? Platforms such as OpenShift are making the transition easier, but there are major differences that architects need to consider. The architecture constraint differences alone are enough to give a systems architect the shivers.

In this presentation we will talk about our experiences moving a cloud-based architecture on Kubernetes to an on-prem solution on OpenShift. We will talk about the differences in architecture constraints, quality attributes, and the developer experience. We'll also talk about the challenges we faced and things we didn't get right.

By the end of the presentation, you will have the knowledge necessary to understand the architectural differences between on-prem and cloud-based systems and the effort required to transition from one to the other. You will also have the knowledge necessary to understand how to build the right way for a hybrid cloud world.

By the end of this session you will also be able to understand the following:

• What architectural considerations to think about when moving a product from cloud to on-prem - or vice-versa
• How to think about reusability when designing systems to enable yourself for moving to a different architecture
• How to mitigate risk when designing features, for future use
• Knowing what it takes to do this kind of work
• What the differences are in API design when transitioning to a new platform, and a new user persona focus