| path | title |
|---|---|
/synthesis/microservices_the_tech |
Synthesis: Microservices: The Tech |
Service Discovery with cheap instances:
Need to answer questions:
- Is there an API that already does what I want?
- What is the team responsible for the API? Standard way for Ops / Monitoring to identify this
- Who is using my API so I know who to tell I'm depreciating it?
- standard way to document request params + responses of hese APIs (random Word documents that may or may not be on the wiki!= discoverable documentation!)
- What team do I call for support / how do I page them when their shit is broken?
<<ServiceDiscovery_Onboarding_New_Employees>>
- "Welcome Mat" for new employees <-- includes pointer to the service discovery document
Don't want a dozen teams deploying their own systems their own way (some will suck). Provide PaaS for microservice deployment with standard quality of service practices.
Provide a very enticing golden path for teams to push to operationalized services. (But know that some can't walk down that path)
you need to provide a rapid, golden path for deploying applications that a team can use to deploy an app quickly. This number needs to go down until it's as close to 0 as possible.
One way monolyths grow: when getting a servicer instance to split this thing into two services is EXPENSIVE. (ie if it takes 4 months to deploy a server, fuck yeah I'll shove everything into one app)
/ build on existing patterns
Fractals are cool