Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Are Your Microservices Naked and Afraid?

312 views

Published on

SpringOne Platform 2016
Speakers: Alan Ho; Head of Developer Programs, Apigee. Sandeep Murusupalli; Solutions Architect, Apigee.

The Cloud is a wild and dangerous place and can create seriously unpredictable traffic to your microservices. Without proper protection & monitoring, your microservices are vulnerable to hackers, self-inflicted denial of service attacks, and extremely high infrastructure costs. Furthermore, as internal data centers begin to mirror the Cloud itself, developers and architects need to rethink services monitoring and protection for both externalized microservice APIs and internal APIs. Attend this session to learn what is the right type of protection (OAuth / Throttling) and monitoring (e.g. bot monitoring) you need to put in place to avoid your microservices becoming a mega-disaster.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Are Your Microservices Naked and Afraid?

  1. 1. ©2015 Apigee Corp. All Rights Reserved. 1 ARE YOUR MICROSERVICES
  2. 2. ©2015 Apigee Corp. All Rights Reserved. First a Story…… 2
  3. 3. ©2015 Apigee Corp. All Rights Reserved. Microservices on the Internet 3
  4. 4. ©2015 Apigee Corp. All Rights Reserved. 4 ?
  5. 5. ©2015 Apigee Corp. All Rights Reserved. 5 Amazon Internal Datacenter circa 2008
  6. 6. ©2015 Apigee Corp. All Rights Reserved. SOLUTION : Zero-Trust Microservices 6
  7. 7. ©2015 Apigee Corp. All Rights Reserved. 5 steps to make this better NO CODE CHANGES NECESSARY !! 7
  8. 8. ©2015 Apigee Corp. All Rights Reserved. Step 1: Setting up a Pass-Through proxies 8 API Gateway Microservice Microservice
  9. 9. ©2015 Apigee Corp. All Rights Reserved. Step 2: Stay on the lookout 9
  10. 10. ©2015 Apigee Corp. All Rights Reserved. Step 3: Protect your backend 10 = BAD
  11. 11. ©2015 Apigee Corp. All Rights Reserved. Micro-circle of doom 11 Spike in Traffic 100% CPU Utilization Poor response time Users Press Refresh / Retry Logic
  12. 12. ©2015 Apigee Corp. All Rights Reserved. Spike Arrest Filtering 12 Spike Arrest Filter
  13. 13. ©2015 Apigee Corp. All Rights Reserved. Step 4: Catch bad API bots 13
  14. 14. ©2015 Apigee Corp. All Rights Reserved. Solution = Machine Learning + Crowdsourcing 14 Company 1 Microservices Company 2 Microservices Traffic Analytics with Machine Learning
  15. 15. ©2015 Apigee Corp. All Rights Reserved. Step 5 – Cache it Don’t Waste it 15
  16. 16. ©2015 Apigee Corp. All Rights Reserved. Joint probability governs microservice behavior 16 # of App Server calls 3 Availability: 97% Assume each service has 99% availability
  17. 17. ©2015 Apigee Corp. All Rights Reserved. Caching the Edge = Instant Cost Reduction & Availability 17 Cache # of App Server calls 1.5 vs 3 Availability: 98.5% vs 97% 50% Cache hit rate
  18. 18. ©2015 Apigee Corp. All Rights Reserved. Cache Analytics 18
  19. 19. ©2015 Apigee Corp. All Rights Reserved. Caching all layers = Instant Cost Reduction & Availability 19 Cache # of App Server calls 1 vs 3 Availability: 99.25% vs 97% 50% Cache hit rate Cache Cache
  20. 20. ©2015 Apigee Corp. All Rights Reserved. Recap of Benefits 1. Proxy with no code changes 2. Find easy opportunities to improve performance 3. Guard against traffic spikes 4. Guard against bots 5. Cache to improve availability + costs 20
  21. 21. ©2015 Apigee Corp. All Rights Reserved. 21 COME BY APIGEE BOOTH TO LEARN MORE

×