Software Architectures for a Single Person Team

Architectures for a single person team

Daniel Cukier @[email protected]

Context: Playax

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

You can’t do everything

The great is the good’s enemy

Technology Choice

core

Know-how

Prob

lem fi

t

Never non-core

Always

KISS

Pareto Rule Extended

Pareto = 80 / 20 Extreme Pareto = 90 / 10 Danieleto = 99 / 1

Monitoring 24/7

new relic

statsd / graphite

Alerting

First thing to do when you wake up

Last thing to do before you sleep

Watch Dogs

TDD or not T

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

Discussions

Stack Overflow Coffee with friends Demos Community events

Reuse: Cloud

As SaaS as possible As PaaS as possible As APIs as possible

Deployments

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

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

Documenting

You can’t do everything

The great is the good’s enemy

Architectures for a single person team

Daniel Cukier @[email protected]