Customer DevOps

Mike's Notes

Here are my working notes from day 9 of building the DevOps Engine for Pipi 9. 

Over the weekend, I attended an excellent film script workshop but managed to work on the DevOps Engine when I wasn't supposed to. Often, I get more done by relaxing and not thinking about a problem. Then, these new ideas start interrupting.

Resources

• https://developer.ajabbi.com/eng/9/report/roadmap.html

Customer DevOps

By: Mike Peters
03/03/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Today, I enabled a separate DevOps Engine for my first customer. Since they will use a multi-tenanted SaaS application, their DevOps engine will also be multi-tenanted.

In this case, their DevOps Engine setup is more about feature requests, customer support, configuration management and automated builds.

Creating a second, customised DevOps Engine helped clarify other practical problems that apply more broadly to building a front-end.

Steps

• DevOps steps use standard workflow processes.
• Moving between these steps uses transition conditions that can change states and trigger other asymmetric processes.

Multi-tenancy

By asking how the chosen tenancy model modified the Pipi instance, I clarified some assumptions and operational rules that result from using multi-tenancy rather than sole tenancy.

• Multi-tenanted SaaS applications for SMEs will use a multi-tenanted Pipi in the back end, which allows less customisation.
• Sole-tenanted SaaS enterprise applications will use a sole-tenanted Pipi in the back end, allowing more customisation.

Deployment

• I figured out a simple way to automatically remove a customer deployment in a multi-tenanted situation, allowing Pipi to close an account.