prototype - Who’s going to create a full management stack before they know the project is worth it?
initial development - If you’re not making it available yet, why does it matter?
early release - It’s available but we haven’t gotten around to managing it, yet. -or- It’s available and we’re so busy supporting it, we don’t have time to implement our management stack.
static references
&
spreadsheets
This might be worse.
This is also perfectly normal.
You might do this because
It's easy
Your architecture is small
Deployment is easy
(or you're really good at it)
you have very limited needs to maintain scalabililty and availability
you have enough engineers and a streamlined enough process that you can use deployment as configuration management
full management
&
service-discovery
This is extraordinary.
This is almost enough.
almostenough
nothing
does not grow beyond one application
unless every application is 100% independent
doesn’t even tackle tracking real or virtual hardware
almost always becomes...
static references / spreadsheets
doesn’t change very quickly
unmanageable at scale
depends on humans
humans generally suck at this
management and service discovery
feels perfect
not perfect
computers miscommunicate
people miscommunicate