Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Pushing the DevOps envelope into the network with microservices

2.443 visualizaciones

Publicado el

A look at microservices and why they are (necessarily) pushing DevOps into the network .

Publicado en: Tecnología
  • Sé el primero en comentar

Pushing the DevOps envelope into the network with microservices

  1. 1. Pushing the DevOps Envelope How Microservices Architecture is Expanding DevOps to the Network Lori MacVittie Principal Technical Evangelist | F5 @lmacvittie
  2. 2. What is (are?) microservices? MONOLITHIC MICROSERVICES
  3. 3. One set of services Many sets of services So?
  4. 4. 25% caching 86%image optimization 45% tcp multiplexing 78% SSLoffloading 34% web acceleration 65% of all apps delivered areweb applications SOURCE: F5 iHealth Mar 2015 38% compression What services?
  5. 5. What other services? SOURCE: F5 iHealth Mar 2015 11% Cookie encryption 1% URLrewriting 59% X-forwarded-for 82%datapath programmability 65% of all apps delivered areweb applications
  6. 6. Some of those services are In the app In the “network” Cookie encryption compression caching URL rewriting load balancing Cookie encryption compression
  7. 7. Monolithic Service Architecture Firewall Core service Infrastructur e App Infrastructur e Core (shared) network App (specific) network Users Apps • Low rate of change • High cost of change • Low tolerance for disruption PRIORITY: RELIABILITY
  8. 8. Firewall Core service Infrastructur e App Infrastructure Microservice Architecture Core (shared) network App (specific) network Users Apps and Services • Low rate of change • High cost of change • Low tolerance for disruption PRIORITY: RELIABILITY • High rate of change • Low cost of change • High tolerance for disruption PRIORITY: AGILITY Per-app service Infrastructure
  9. 9. Firewall Core service Infrastructure App Infrastructure Per-app service infrastructure Microservice Architecture Core (shared) network App (specific) network Users Apps and Services • Low rate of change • High cost of change • Low tolerance for disruption • High rate of change • Low cost of change • High tolerance for disruption DevOps Today Needs DevOpsing
  10. 10. Some services in need of DevOps are In the network caching URL rewriting load balancing Cookie encryption compression
  11. 11. Which is a problem because of IT professionals surveyed say that once an application completes the dev process, it takes a week or more to move into production; for 14% of those, it’s a month or more. 43 PERCENT Data: InformationWeek 2014 DevOps Survey, ESG Organizations citing biggest challenge to application deployments is time to provision N ETW OR K services.44 PERCENT
  12. 12. Why is that? CHANGES CAUSE SERVICE DISRUPTION NETWORK CHANGES ARE SLOW 24% 22% 16% 12% HARD TO MANAGE CHANGES TO THE NETWORK APPLICATION CHANGES REQUIRE NETWORK CHANGES Source: IDC's Why the Network Matters Survey - November, 2012
  13. 13. How do we fix that?
  14. 14. DevOps the Network Things
  15. 15. DevOps the Network Things • Frictionless software • Per Application deployment • Scale Out software-only • Low-cost / No-cost • APIs, SDKs and community • Integration with tools (Puppet/Chef)
  16. 16. Firewall Core service Infrastructure App Infrastructure Per-app service infrastructure Core (shared) network App (specific) network Users Apps and Services • Low rate of change • High cost of change • Low tolerance for disruption • High rate of change • Low cost of change • High tolerance for disruption DevOpsing the network leads to a microservices-friendly environment
  17. 17. Thank You @lmacvittie

×