Explore >> Select a destination
|
You are here 
|
www.syntasso.io | ||
| | | | |
www.loft.sh
|
|
| | | | | As your organization grows, deploying your software and maintaining all related systems can become more complex. This complexity, along with the desire to own the infrastructure stack without needing workarounds for off-the-shelf tools, drives many teams to implement an internal developer platform (IDP). | |
| | | | |
humanitec.com
|
|
| | | | | An Internal Developer Platform (IDP) is the sum of all the tech and tools that a platform engineering team binds together to pave golden paths for developers. IDPs lower cognitive load across the engineering organization and enable developer self-service, without abstracting away context from developers or making the underlying tech inaccessible. Well designed IDPs follow a Platform as a Product approach, where a platform team builds, maintains and continuously improves the IDP, following product management principles and best practices. | |
| | | | |
sookocheff.com
|
|
| | | | | Infrastructure is undergoing a significant paradigm shift. At my first job as a software developer, scaling our infrastructure meant buying a physical machine and installing it in a rack, setting up the system images and base software by hand, configuring the network using some shell scripts, and finally, making it available for developers to install software. Now, with the advent of cloud computing, the same capabilities - installing and running software - are available on-demand. | |
| | | | |
www.syntasso.io
|
|
| | | You can follow the supposed "best practices" in building an Internal Developer Platform (IDP)and still end up with something people avoid. If top-down and bottom-up approaches don't fully address the internal developer platform problem, and platform orchestration is the missing piece that connects the dots and bridges the gap, what is platform orchestration? | ||
