To Infinity ... and Beyond!

This talk was presented at the Austin Cloud Users meetup group, and discusses what Service Oriented Architecture is, and how you can use it to build a scalable web application.

Transcript

1. To Infinity ... and Beyond! Scaling Your Stack with Service Oriented Architecture
2. In a Past Life ... GET /v2/phone/+18182179229 {“name”: “DEGGES,RANDALL”}
3. Scaling OpenCNAM 1,000,000s to ... 1,000,000,000s
4. Reduced Cost By 50%
6. What You’ll Learn • Why scaling is hard. • What SOA is. • How SOA can help you. • How to implement SOA. • When not to use SOA.
7. Yo, I’m Randall • Developer Evangelist @ Stormpath • I blog: http://www.rdegges.com • I code: https://github.com/rdegges • I tweet: @rdegges • Email me: randall@stormpath.com
9. The Problem
10. Scaling Web Apps is Hard
11. If You Need to Scale...
12. Let’s talk about how most people build applications.
15. Part 1 What’s the deal with monolithic apps?
16. Fighting Your Code Base
17. Features Fight for Resources
18. Catastrophic Failure
19. Resource Allocation Problems
20. Part 2 What’s SOA?
23. The UNIX Way Write programs that do one thing and do it well. Write programs to work together. Write programs that speak HTTP, because that is a universal interface.
24. $ find /path/to/search/ \ -type f -iname "*.mp4" \ -printf '%s %p\n'| \ sort -nr | head -10 The UNIX Way
25. Part 3 Why is SOA so great?
26. Simplicity be happier ^^ be more productive!
27. Isolated Failure
28. Simple Scaling
29. $ heroku addons:add heroku-postgresql:fugu --fork HEROKU_POSTGRESQL_RED $ git push heroku master $ heroku scale web=2 $ heroku scale worker=2
31. Reduced Cost
32. Part 4 Migrating to SOA
33. Focus on What You’re Best At
34. The Best Code is the Code You Don’t Write
36. Isolate Components • myapp-www • myapp-billing • myapp-callerid • myapp-dashboard • myapp-docs
37. SOA Flow
38. Define API Specs • GET /v1/phones • GET /v1/phones/+18182179229 • POST /v1/phones • PUT /v1/phones • PATCH /v1/phones • DELETE /v1/phones
39. TIPS for Designing Good APIs http://www.stormpath.com/blog/designing-rest-json-apis
41. Don’t Forget! • Play to your strengths. • Don’t worry about tools and languages. • Give your team freedom! • Services should be small enough to build in a few days.
42. SOA Downsides
43. Don’t Use SOA If Your Project is Unstable
44. Don’t Use SOA If Don’t Know APIs
46. Recap • Monolithic apps are hard to maintain and scale • SOA apps require upfront work, but scale easily • SOA apps are easier to maintain • SOA apps can save you money
47. Questions? 818-217-9229