PaaS Vs Custom Orchestrator for PaaS

Let me explain what I am comparing here. PaaS can be any Platform offering from Azure, GCP or AWS. By Wrapper /Custom Orchestrator I mean a portal developed in house to unify experience and standardize tools across organization.
The advantage of going with straight PaaS offering is you will have all the benefits of innovation from your cloud service provider. Resource you are hiring from external will already equipped with knowledge and day 1 productivity is possible. No need to maintain training sessions for employees as there are so many trainings available online for free. Access to the cloud provider portal can be controlled per department by subscription. This way budget can still be tracked by grouping all the subscriptions in the division. The power of portal, CLI tools can be leverage along with straight hooks for the DEV tools/studios. Innovations and integrations provided by cloud vendor can be experimented as soon as they hit the market.
Coming to the disadvantages , going to one cloud provider PaaS service is vendor lock in. you are so much dependent on that vendor and costs can go high in the long run, you might be left with no option other than to pay. You might be too dependent on the services and tightly coupled your critical work loads and customer journeys, you may not be able to function without it.
Now lets talk about the Custom Orchestrator idea. Here we are talking about Terraform enterprise for leveraging provision of service underneath a portal for unified experience. If your organization is using multiple cloud vendors or planning to use in the future this will be a better approach. You are providing unified user experience irrespective of PaaS service your teams are leveraging. you can extend the same portal/unified experience to drive them towards better strategy of K8's or serverless based on workload. You will have a single entry point and governance.
Some disadvantages with custom orchestrator is you have to develop unified portal and train your employees to use it. There will be some learning curve for understanding the portal. It will take time for you to implement innovations from cloud provider. You have to maintain a team to develop, document, train and implement updates.
My vote will always be for unified experience portal, Terraform underlying execution with gitops kind of development towards K8's. I know I haven't touched on lot of topics in this matter, it is a mini comparison.

Comments

Popular posts from this blog

Dhirubhai Notorious or Famous???????

Sri Sri kavitha

Excerpt from the book "Made to Stick"