This document discusses architectures for a single person development team. It recommends focusing on the core problem and technology, monitoring systems 24/7, writing tests for core functionality, reusing cloud services when possible, and deploying with minimum downtime through automated processes. Documentation of core diagrams, scripts, and models is also suggested.

1. Architectures for a single person team
Daniel Cukier @danicukidanicuki@ime.usp.br

2. Context: Playax
Startup!
6000 radios, sites, TVs
800K tracks
1M detections / day
10M API calls / day
35 VMs

4. You can’t do everything
The great is the
good’s enemy

5. Technology Choice
core
Know-how
Problemfit
Never non-core
Always

6. KISS

7. Pareto Rule Extended
Pareto = 80 / 20
Extreme Pareto = 90 / 10
Danieleto = 99 / 1

8. Monitoring 24/7

9. new relic

10. statsd / graphite

11. Alerting

12. First thing to do
when you wake up
Last thing to do
before you sleep

13. Watch Dogs

14. TDD or not T
Tests on core
Copy & Paste
prototypes
Test and refactoring
(or not) when
prototype survives
The team will fix

15. Discussions
Stack Overflow
Coffee with friends
Demos
Community events

16. Reuse: Cloud
As SaaS as possible
As PaaS as possible
As APIs as possible

17. Deployments
Minimum or no-downtime
git push
Critical things on Saturday Carnival 2am
Cloud images

18. Core diagrams
Infrastructure scripts
Database model
http://yuml.me/
Documenting

19. You can’t do everything
The great is the
good’s enemy

20. Architectures for a single person team
Daniel Cukier @danicukidanicuki@ime.usp.br