Downloaded 11 times
Uploaded byJohn Barton
Minimum Viable Architecture For Web Apps
The document discusses architectural best practices for web applications, particularly in small, fast-growing companies, emphasizing the need for balance in system design. It recommends using cloud infrastructure with a focus on security, outlining specific components for an architecture, along with insights on maintaining clear ownership within teams. Additionally, it provides security tips and a list of recommended reading for further exploration of the topic.
Minimum Viable Architecture For Web Apps
- 1.
- 2. Hi, I'm @johnbarton,Director of Engineering at 99designs
- 3. WhyYou Should Listen ToMe™ How I think About Architecture. Based on Actual Architecture How Do I Architect? Specifically in Smaller, Fast Growing Companies Apologies for undercookedness, I am still jetlagged A Lightly Structured Series of Rants Your Web Application Should Look Like This Security #protips Recommended Reading (Do Kids Still Read Today?)
- 4. There are reasons WhyYouShould ListenTo Me™
- 5. Because I aman "industry speaker", clearly.
- 7. MyCareer: ASP.NET +MSSQL Envato: Ruby on Rails + MySQL Goodfilms: Ruby on Rails + PostgreSQL 99designs: PHP, Ruby on Rails, Go + MySQL + lots of random consulting
- 8. Based on ActualArchitecture How I think About Architecture.
- 12. "organisations which designsystems ... are constrained to produce designs which are copies of the communication structures of these organisations" - M. Conway
- 13. Specifically in Smaller,Fast Growing Companies How Do I Architect?
- 14. Typically the systemsI see are either woefully over or under architected. The balance is hard to get right, and harder to keep right.
- 15. YAGNI and Respondingto Change
- 16. “If you wantto build a ship, don’t drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea.” - Antoine de Saint-Exupéry
- 17. No Exceptions. YourWeb ApplicationShould Look LikeThis
- 18. Put these thingsinto "the cloud" and put your code in there 1 x Load Balancer 2 x Web Server 1 x Database Master + 1 x Read Replica 1 x Async Queue Processor Firewall the lot at the outside, and iptables each box too Share nothing except database (and maybe session store)
- 19. The Single ResponsibilityPrinciple + Zero, one, and many.
- 20. Inflection Point: ~15 Developersor ~100M Weekly Page Impressions
- 21. Upgrade to SOAat the same time you split teams Have clear lines of ownership from teams to systems Do not create a service without a dedicated team or n > 1 clients
- 22.
- 24. Don't build abitcoin exchange or wallet "Outsource" the security design: use a secure by default framework AUDIT TRAIL AUDIT TRAIL AUDIT TRAIL You are more likely to get audited than get hacked unless you are dumb Security Protips Apply the Mickens "Mossad/Not Mossad" Threat Model Keep your mouth shut around 4chan and other angry intelligent people For The Love of God Don't Leave a Laptop on a Train or in the Pub
- 25. Here are somebooks I like. Also, some things that are not books. Recommended Reading
- 26. "hominem unius libritimeo"
- 35.
- 36. I have noidea why our company slide-theme has one with clouds on it Thanks for listening! http://99designs.com