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.

Microservices architecture

270 views

Published on

Microservices architecture

Published in: Software
  • Be the first to comment

  • Be the first to like this

Microservices architecture

  1. 1. Developing a single application as a suite of small services
  2. 2. Wave of Innovation in software engineering http://container-solutions.com/microservices-artificial-intelligence-os/
  3. 3. 0 10 20 30 40 50 60 70 2013 2014 2015 2016 Market Trend Google trend
  4. 4. http://blog.trifork.com/2015/04/29/goto-amsterdam-2015-the-microservices-track/ Hype Cycle Chasm marketing
  5. 5. Technical Evangelism & Development TeamDX Microsoft Confidential Where we started… It has been an enduring approach Develop Codify Communicate Learn “Become a leading technical expert and trusted partner” Evangelism ISV
  6. 6. Developing a single application as a suite of small services
  7. 7.      
  8. 8. Frontends StorageMiddle Tier • Stateless frontends • Stateless middle tier • Storage is the bottleneck • Latency • Throughput • Scalability • Horizontal calls are problematic • Data shipping (paradigm)
  9. 9. Silver bullet ?
  10. 10. Silver bullet ?
  11. 11. Silver bullet ?
  12. 12. Browser
  13. 13. available scalable agile
  14. 14. Common characteristics
  15. 15. 1. 2. 3. 4. 5. 6. 7. 8. 9.
  16. 16.   1. Componentization via services
  17. 17. 2. Organized around business capabilities
  18. 18. Monolithic Microservices 2. Organized around business capabilities
  19. 19. Monolithic Microservices 6. Decentralized Data Management
  20. 20. Direct Client-to-Microservice Communication Using an API Gateway
  21. 21. Werner Vogals, VP, Amazon
  22. 22. • Single-purpose • Connect only through APIs • Connect over HTTPS • Largely “black boxes” to each other
  23. 23. Journey to the microservcies August, 2008
  24. 24. • Test resiliency and Recovery of AWS • Simulate failures of instance of service • Shutting down one or more of VMs
  25. 25. Why Microservices? Pre-history Dispatch Core Services Maps Data Metrics PHP(outsourced) Node.js, moving to Go Python, moving to Go Python and Java Python and Java Go Move and release independently Own your Uptime Use the “best” tool for the job
  26. 26. https://martinfowler.com/articles/microservice-trade-offs.html
  27. 27. Microservices Concerns
  28. 28. Fast, agile, inexpensive, and massively scalable infrastructure, offered fully self-service and with pay-as-you-go billing
  29. 29. Manage Container applications using familiar tools Scale and orchestrate using DC/OS, Docker Swarm, or Kubernetes Use popular open-source tooling Migrate container workloads to and from Azure Azure Container Service Create an optimized container hosting solution
  30. 30. Container Platform Container Dashboard Docker Universal Control Plane Container Orchestration Container Engine Operating System Linux, [windows] Linux, [windows] Linux
  31. 31. Azure Windows Server Linux Hosted Clouds Windows Server Linux Service Fabric Private Clouds Windows Server Linux High Availability Hyper-Scale Hybrid Operations High Density Microservices Rolling Upgrades Stateful services Low Latency Fast startup & shutdown Container Orchestration & lifecycle management Replication & Failover Simple programming models Load balancing Self-healingData Partitioning Automated Rollback Health Monitoring Placement Constraints
  32. 32. Too stressed Processor, Memory & Network Too many noisy microservices neighbors Can handle more microservices Cluster's automatic Resource-Balancing in Service Fabric VM crashes!!
  33. 33. Developing a single application as a suite of small services

×