Spider Architecture
•Télécharger en tant que ZIP, PDF•
5 j'aime•1,273 vues
Talk from GlueCon 2012 in Denver, CO on the advent of service-oriented architectures for mobile and web backends where each of the services is managed by a third-party. This structure was first popularized by Heroku's addons ecosystem.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Spider Architecture
Similaire à Spider Architecture (20)
Dernier
Dernier (20)
Spider Architecture
- 1. Exploring the Spider Architecture Marc Weil Founder & CTO, CloudMine marc@cloudmine.me @marcweil
- 2. Where we’ve come from (and, in many cases, where we are)
- 3. Presentation Business Logic Database
- 4. Monolith
- 5. One example... (at least by default)
- 6. Why?
- 7. Why? • Many libraries push responsibility from Nginx/Apache to Rails
- 8. Why? • Many libraries push responsibility from Nginx/Apache to Rails • Same with database
- 9. Why? • Many libraries push responsibility from Nginx/Apache to Rails • Same with database • The business logic ends up doing far more than business logic should
- 10. Why is this a problem?
- 11. Why is this a problem? • Requires lots of code that doesn’t contribute to core value
- 12. Why is this a problem? • Requires lots of code that doesn’t contribute to core value • Increases entropy of codebase
- 13. Why is this a problem? • Requires lots of code that doesn’t contribute to core value • Increases entropy of codebase • Difficult to separate and scale different components
- 14. Rails is one example, but this is common
- 15. As scale requirements increase, monolithic architectures break down
- 16. As scale requirements increase, monolithic architectures break down More responsibility in code = more codebase entropy
- 17. What’s easier?
- 18. Self-contained, focused components
- 19. From
- 21. Many small services Keeps codebases small Enables polyglotism Increases team focus >1 point of failure
- 23. Scale it up!
- 24. But it’s not all rainbows and butterflies
- 25. But it’s not all rainbows and butterflies More complex deployment story
- 26. But it’s not all rainbows and butterflies More complex deployment story Increases ops requirements
- 27. But it’s not all rainbows and butterflies More complex deployment story Increases ops requirements Potentially higher costs
- 28. But it’s not all rainbows and butterflies
- 31. We’ve moved from in-house to managed
- 32. How did this help business?
- 33. How did this help business? Reduce staff requirements
- 34. How did this help business? Reduce staff requirements Increase focus on core value (is your business’ value really to keep servers up?)
- 35. How did this help business? Reduce staff requirements Increase focus on core value (is your business’ value really to keep servers up?) Decrease time to market
- 36. Adoption of IaaS made PaaS possible etc etc (there are a ton)
- 40. Let’s bring it all back together
- 41. +
- 42. =
- 45. Redis SendGrid MySQL Glue Urban Geo Airship S3
- 46. Your mobile app’s backend Redis SendGrid MySQL Glue Urban Geo Airship S3
- 47. How does this help business?
- 48. How does this help business? Reduce staff requirements
- 49. How does this help business? Reduce staff requirements Increase focus on core value (is your business’ value really to administer Redis and RabbitMQ?)
- 50. How does this help business? Reduce staff requirements Increase focus on core value (is your business’ value really to administer Redis and RabbitMQ?) Decrease time to market (focusing only on your core value means there’s less work for you to do)
- 51. Simple Example
- 52. “A geo-fence is a virtual perimeter for a real-world geographic area.” - Wikipedia
- 55. in g! D
- 56. So how does it work?
- 57. Three steps 1. Device registration 2. Determine when current location crosses geofence boundaries 3. Send push notifications* * Beware hidden complexity
- 59. Queue Register Web Services Register
- 60. Queue Register Web Services Fairly complicated process Register
- 61. Queue Register Web Services Expensive Fairly complicated process and complex Register
- 62. Web Services Record ID Register
- 63. Web Services Expensive Record and complex ID Register
- 64. Register Web Services Expensive Record and complex ID
- 65. Record ID Register
- 68. Processing... Send a push, please!
- 69. Processing... Send a push, please! Expensive and complex
- 70. Processing... Send a push, please! Expensive and complex Complex
- 71. Processing... Send a push, please! Expensive and complex
- 72. Processing... Send a push, please!
- 73. ~15 lines of server-side code in this example
- 74. Build on the shoulders of giants
- 75. Stop re-inventing the wheel
- 76. The UX of your client-side is key Invest the appropriate amount of resources
- 77. Opinion time
- 78. Inquiring minds want to know...
- 79. Is this kind of architecture better reflected by or ?
Notes de l'éditeur
- \n
- \n
- \n
- \n
- \n
- Libraries treat nginx and database as dumb components. Push everything into Rails.\n
- Libraries treat nginx and database as dumb components. Push everything into Rails.\n
- Libraries treat nginx and database as dumb components. Push everything into Rails.\n
- \n
- \n
- \n
- \n
- Harder to maintain and tune as scale increases\n
- \n
- \n
- From monolithic to distributed\n
- \n
- \n
- \n
- Now you need a queuing process (AMQP, 0MQ, RabbitMQ, etc)\nMore and different server images\nPotentially costs more\n
- Now you need a queuing process (AMQP, 0MQ, RabbitMQ, etc)\nMore and different server images\nPotentially costs more\n
- Now you need a queuing process (AMQP, 0MQ, RabbitMQ, etc)\nMore and different server images\nPotentially costs more\n
- Now you need a queuing process (AMQP, 0MQ, RabbitMQ, etc)\nMore and different server images\nPotentially costs more\n
- Now you need a queuing process (AMQP, 0MQ, RabbitMQ, etc)\nMore and different server images\nPotentially costs more\n
- Now you need a queuing process (AMQP, 0MQ, RabbitMQ, etc)\nMore and different server images\nPotentially costs more\n
- Now you need a queuing process (AMQP, 0MQ, RabbitMQ, etc)\nMore and different server images\nPotentially costs more\n
- Let’s pause for a moment and talk about another set of advancements we’re all familiar with.\n
- \n
- \n
- \n
- \n
- \n
- Now you don’t even have to manage your own servers, which IaaS still requires you to do\nJust push code and go\n
- Let’s focus on Heroku for just a moment\n
- It introduced a plugin system. Look at this small fraction of things!\n
- It introduced a plugin system. Look at this small fraction of things!\n
- \n
- \n
- \n
- \n
- \n
- \n
- This is the spider architecture. Gluing together external services with a small amount of custom code to create a fully-functioning application.\n
- Does this look familiar?\n
- Does this look familiar?\n
- Does this look familiar?\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Competing with experiences given by Path, Instagram, etc.\nPeople expect near-perfect UX, and it’s not trivial to accomplish.\n
- \n
- \n
- \n
- \n