Opinions

1. Keep it simple
2. Create useful abstractions
3. Build something you’re proud of
4. Avoid broken windows
5. Naming is important
6. Automate testing and deployment
7. Avoid handling base exceptions
8. Instrument all I/O
9. Be prepared for outages
10. Use linting to set standards
11. Reduce depencies
12. Document using how to’s and clean code
13. Optimize reads <100ms
14. Minimize the write path <100ms
15. Make writes idempotent
16. Use retries and timeouts to improve reliability
17. Events are helpful, but introduce complexity
18. Aim for one service per team
19. Scale horizontally

Let's Talk

Reach out to us at dan@app-vitals.com, and let’s build something amazing together.