-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Platform Engineering] Blog #1 "Pulumi Patterns and Practices (P3): A Pulumi-based reference architecture for large-scale organizations" #12414
Conversation
Your site preview for commit 123a553 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-12414-123a5536.s3-website.us-west-2.amazonaws.com. |
|
||
Pulumi can help bring consistency to your software catalog by encoding design patterns into reusable *[component resources](https://www.pulumi.com/learn/abstraction-encapsulation/component-resources/)* and by building custom *[organization templates](https://www.pulumi.com/docs/pulumi-cloud/developer-portals/templates/)* that provide a no-code or low-code way to start a new project. Templates help get projects off the ground faster and ensure consistent code structure, policy compliance, and best practices. | ||
|
||
<figure> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like video of an older version of NPW.
So you'll want to use an updated video.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Some comments
|
||
There are quite a few listicles out there professing to authoritatively tell you the 5, or 7, or 11 essential components of an internal developer platform. Personally, I trust our customers to tell us, and here's what they have said they need: | ||
|
||
**Consistency:** Bring some order to the chaos. As your company and your infrastructure grows, it gets more and more complicated to maintain consistency. You might already have established design patterns that you want to replicate, but don't have any way to encode those practices in your current tools. There's a lot of copy/paste of reusable blocks, but no way to apply [DRY principles](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself) or to modularize/templatize the important parts (hint: all the parts are important!). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on this amazing list...
I think we should either update this https://www.pulumi.com/what-is/what-is-platform-engineering/ or create a brand new page called "What is an internal developer platform". I like your points, they are slightly similar to the requirements of that page, but more colloquial in how they are written.
|
||
We have an idea of how you can use all the Pulumi products together to deliver a comprehensive internal platform for security, infrastructure management, and deployments. Call it an internal platform for developer platform engineers (IPfDPE), if you want. We call it the realization of a vision we've been working hard to build for many years. | ||
|
||
The **Platypus Platform** is a reference architecture that we will be describing, and providing code for, through this series of articles. We'll be diving deep into not just what you can do with our tools, but how to do it, and provide code for a reference implementation that you can use to jump start the process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just call it the "Platyform" as shorthand? otherwise Platypus Platform gets a bit long in how its written
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i decided to just called it Platypus, and refer to it as a "reference architecture for a Pulumi-based internal developer platform".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Naming seems to still be an open question here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going with Pulumi Patterns and Practices (P3).
Your site preview for commit aac44d6 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-12414-aac44d6f.s3-website.us-west-2.amazonaws.com. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, just need meta image update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, just need meta image update
Your site preview for commit 5502e10 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-12414-5502e106.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 1cd6e75 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-12414-1cd6e758.s3-website.us-west-2.amazonaws.com. |
Pushing out as-is and will update the video later today when we have images available (deadlines!).
First of a series of blog posts about Pulumi Patterns and Practices (P3) reference architecture (a rebranded version of internal demo Pequod).