Silo-Based architectures for High Availability Application @ Music City Code

High availability is becoming a de-facto requirement of today's applications. Customer-facing IT failures mean directly losing customer revenue and trust, as users have grown accustomed to easily switching service providers for more reliable ones. Lack of internal systems availability block employee productivity and add to the financial burden. Thus, it is critical to have a healthy, performant, resilient IT structure serving as a backbone of conducting your business. But there are no textbook solutions to achieving five 9s availability. Data redundancy, computing clusters, load balancing, fail-over mechanisms, each of these individually addresses one potential issue, but none treats systems in your organisation holistically for maximising business revenue. Silos are a clever method of grouping servers in such a way that they can be scaled both horizontally and vertically, depending on the actual application needs. Most importantly, it frees you from over-optimizing the architecture upfront, by allowing fine adjustments easy to integrate in your Agile workflow.

Transcript

2. FOR HIGH AVAILABILITY APPLICATIONS SILO-BASED ARCHITECTURES Music City Code 2016 @gbtekkie
3. 3 ✤ Geek. Mother. Do-er. ✤ Crafting enterprise- level apps ✤ on LAMP stack since 2003 ✤ Architecture and DevOps consultant ✤ PHP Cluj Meetup Organizer Georgiana Gligor
4. 4 AGENDA ✤ who needs to address high availability? ✤ describe high availability ✤ silos: a possible approach ✤ advantages and disadvantages
5. Software industry is built around anticipating change. - David Scott Bernstein, “Beyond Legacy Code” 5
6. YOUR APPLICATION
10. master Frontend Business Logic Frontend Frontend Browser internet Load balancer slave reads writes 10 ADJUSTING
11. master Frontend Business Logic Frontend Frontend Browser internet Load balancer slave reads writes 11 ADJUSTING redundancy
12. master Frontend Business Logic Frontend Frontend Browser internet Load balancer slave reads writes 12 ADJUSTING resilience
13. 13 TYPICAL LAYERING
14. 14 APP COMPONENTS
15. HIGH AVAILABILITY
16. 16 Ability to access the system: ✤retrieve information ✤alter information ✤send new data - Availability
17. 17 DOWNTIME ✤ scheduled ✤ unscheduled
18. 18 THE 9s DANCE Uptime Shortname Downtime (per year) 90.000 % one nine 36.5 days 99.000 % two nines 3.65 days 99.900 % three nines 8.76 hrs 99.990 % four nines 52.56 mins 99.999 % five nines 5.26 mins
19. 19 A man’s got to know his limitations. - Dirty Harry
20. 20 HA SYSTEM 1. eliminate single points of failure 2. reliable crossover 3. detect failures as they occur
21. SILOS
22. 22 Departments inside a company don’t work together. - Silo Mentality
23. 23 USER BEHAVIOUR amazon facebook youtube Alexa Rank 6 3 2 daily time on site 12:07 mins 19:27 mins 23:44 mins daily pageviews / visitor 11.83 9.38 12.84 bounce rate 21.50 % 29.50 % 33.50 %
24. 24 FIXTURE-BASED DEVELOPMENT
25. 25 HAPPENS TO THE BEST
26. 26 SILO-BASED ARCHITECTURE
27. 27 MULTIPLE CACHES
28. 28 A/B TESTING
29. 29 GEOGRAPHICAL DISTRIBUTION
30. 30 LIVE UPGRADES
31. 31 ADVANTAGES ✤ real A/B testing ✤ no BHUF requirements ✤ no disruption => brand loyalty ✤ lower TCO ✤ simplify scalability ✤ avoid unneeded complexity, reuse familiar tech
32. 32 DISADVANTAGES ✤ needs razor-sharp DevOps team ✤ small increase in hardware costs on kick-off ✤ adds complexity to the monitoring layer ✤ reconsider traceability ✤ different bug reproducing and hunting
33. TAKEAWAYS
35. 35 ✤ build situational awareness with clever monitoring ✤ automate outage detection ✤ powerful A/B testing ✤ think long-term TAKEAWAYS
36. 36 FURTHER READING ✤ Wikipedia HA page ✤ OpenStack’s HA concepts ✤ Merge Hemo report from FDA ✤ USA Presidential Policy Directive 21 ✤ “Beyond Legacy Code” book
37. Q & A g@polyglots.tech @gbtekkie
38. Georgiana Gligor 38 THANK YOU