Successfully reported this slideshow.
Your SlideShare is downloading. ×

Event driven infrastructure

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Upcoming SlideShare
DevOps and AWS
DevOps and AWS
Loading in …3
×

Check these out next

1 of 33 Ad

More Related Content

Slideshows for you (20)

Similar to Event driven infrastructure (20)

Advertisement

More from Shiva Narayanaswamy (17)

Recently uploaded (20)

Advertisement

Event driven infrastructure

  1. 1. EVENT  DRIVEN  INFRASTRUCTURE   DevOpsDays  Melbourne,  2015   Shiva  N  (@shivamaan)  
  2. 2. A  BANANA  WAREHOUSE  AT  THE  ZOO  
  3. 3. RUN  A  BANANA  INVENTORY  EVERY  HOUR  
  4. 4. GIVE  ME  5  BANANAS  
  5. 5. MONKEY  TOOK  5  BANANAS   Run  a  banana   inventory   Plot  monkeys   banana  consumption   pattern       Analytics  on   monkey  banana   consumption  across   all  zoos    
  6. 6. EVENT  DRIVEN  INFRASTRUCTURE  
  7. 7. Event  Bus   Event   Producers   Event   Transport   Event   Consumers  
  8. 8. - Real  time  (or  near  real  time)   - Push  notifications   - One-­‐way  ‘fire-­‐and-­‐forget’   - Immediate  action  at  event  consumer   - Informational  (“monkey  took   bananas”)  and  not  commands   (“perform  banana  inventory”)   5  CHARACTERISTICS  
  9. 9. WHY?   - Decouple  responsibilities   - Communicate  by  triggering  events   - Scale  out  components  horizontally   - Higher  responsiveness   - High  availability  &  Resiliency  
  10. 10. WHAT  ABOUT  INFRASTRUCTURE?  
  11. 11. AUTOMATED  CONFIGURATION   MANAGEMENT   - Puppet   - Chef   - Ansible   - Salt   - Etc.  
  12. 12. INFRASTRUCTURE  AS  CODE   CLOUDFORMATION  +  CUSTOM  RESOURCES  =  NO  LIMITS  
  13. 13. STACKSTORM  
  14. 14. HOMEGROWN  TOOLS/SCRIPTS  
  15. 15. AWS  LAMBDA   A  whole  new  world  
  16. 16. -  A  zero-­‐administration  compute  platform   -  Stored  procedures  for  the  cloud   -  Function-­‐as-­‐a-­‐Service  (NodeJS/Java)     -  Event  driven  from  other  services     -  …or  triggered  externally  and  even   chained   WHAT  IS  LAMBDA?  
  17. 17. WHAT  EVENTS  DOES  YOUR   INFRASTRUCTURE  REACT  TO?  
  18. 18. SIMPLE  EVENTS  
  19. 19. SPIKY  LOAD  EVENTS   -  Pre  warming  (Time)   -  Auto  scaling  (Metrics)   -  Feed  forward  loops   (Predictive)    
  20. 20. COMPONENT  FAILURE  EVENTS   - EC2  auto  healing   - SQS  design  pattern   - Service  discovery  +  Container   recycling   – Consul   – Serf  
  21. 21. DISASTER  RECOVERY  EVENT  
  22. 22. SECURITY  EVENTS   - DDos  Attacks   - Instance  compromise  
  23. 23. STREAMING  EVENTS   Cloudtrail  logs   streaming  to   Cloudwatch   Subscribe  Kinesis   stream  to   Cloudwatch  logs   Lambda  func8on   subscribed  to   Kinesis  watching   for  pa:erns   SNS  no8fica8on  for   insecure  pa:erns  in   Cloudtrail  logs  
  24. 24. COMPLEX  EVENTS   - Event  Observer  Pattern   - Intelligent  build  pipelines  
  25. 25. SENTIENT  EVENTS  ?!  
  26. 26. HOW  DOES  THIS  AFFECT  “THE   DEVOPS”  
  27. 27. OPERATIONAL  LIFECYCLE   – Immutable  infrastructure   – No  patching  or  in  place  deployments  
  28. 28. SERVERLESS  ARCHITECTURES  
  29. 29. MONITORING  AND  METRICS   – Centralized  logging   – Log  Analytics   – Build  metrics,  application  metrics,   customer  experience  metrics  instead   of  CPU,  memory  and  OS  metrics   – Event  Storms      
  30. 30. IS  THIS  A  SCARY  PATH?  
  31. 31. THANK  YOU  

×