Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Architectures for a single person team
Daniel Cukier @danicukidanicuki@ime.usp.br
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
Problemfit
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 @danicukidanicuki@ime.usp.br
Software Architectures for a Single Person Team
Upcoming SlideShare
Loading in …5
×

Software Architectures for a Single Person Team

1,057 views

Published on

Software Architectures for a Single Person Team

Published in: Technology
  • Be the first to comment

Software Architectures for a Single Person Team

  1. 1. Architectures for a single person team Daniel Cukier @danicukidanicuki@ime.usp.br
  2. 2. Context: Playax Startup! 6000 radios, sites, TVs 800K tracks 1M detections / day 10M API calls / day 35 VMs
  3. 3. You can’t do everything The great is the good’s enemy
  4. 4. Technology Choice core Know-how Problemfit Never non-core Always
  5. 5. KISS
  6. 6. Pareto Rule Extended Pareto = 80 / 20 Extreme Pareto = 90 / 10 Danieleto = 99 / 1
  7. 7. Monitoring 24/7
  8. 8. new relic
  9. 9. statsd / graphite
  10. 10. Alerting
  11. 11. First thing to do when you wake up Last thing to do before you sleep
  12. 12. Watch Dogs
  13. 13. TDD or not T Tests on core Copy & Paste prototypes Test and refactoring (or not) when prototype survives The team will fix
  14. 14. Discussions Stack Overflow Coffee with friends Demos Community events
  15. 15. Reuse: Cloud As SaaS as possible As PaaS as possible As APIs as possible
  16. 16. Deployments Minimum or no-downtime git push Critical things on Saturday Carnival 2am Cloud images
  17. 17. Core diagrams Infrastructure scripts Database model http://yuml.me/ Documenting
  18. 18. You can’t do everything The great is the good’s enemy
  19. 19. Architectures for a single person team Daniel Cukier @danicukidanicuki@ime.usp.br

×