Developing a single large application as a suite of small microservices can provide benefits like improved scalability, agility, and the ability to update parts of the application independently. Some common characteristics of the microservices approach include designing systems around business capabilities, decentralized data management, and direct client-to-microservice communication through an API gateway. There are also concerns to consider like increased complexity and the need for robust monitoring.

3. Developing a single application as a suite of small services

5. Wave of Innovation in software engineering
http://container-solutions.com/microservices-artificial-intelligence-os/

6. 0
10
20
30
40
50
60
70
2013 2014 2015 2016
Market Trend
Google trend

7. http://blog.trifork.com/2015/04/29/goto-amsterdam-2015-the-microservices-track/
Hype Cycle
Chasm marketing

8. 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

9. Developing a single application as a suite of small services

10. 






11. Frontends StorageMiddle Tier • Stateless frontends
• Stateless middle tier
• Storage is the bottleneck
• Latency
• Throughput
• Scalability
• Horizontal calls are problematic
• Data shipping (paradigm)

12. Silver bullet ?

13. Silver bullet ?

14. Silver bullet ?

15. Browser

16. available scalable
agile

21. Common characteristics

22. 1.
2.
3.
4.
5.
6.
7.
8.
9.

23. 

1. Componentization via services

24. 2. Organized around business capabilities

25. Monolithic Microservices
2. Organized around business capabilities

26. Monolithic Microservices
6. Decentralized Data Management

29. Direct Client-to-Microservice Communication Using an API Gateway

32. Werner Vogals, VP, Amazon

33. • Single-purpose
• Connect only through
APIs
• Connect over HTTPS
• Largely “black boxes”
to each other

37. Journey to the microservcies
August, 2008

39. • Test resiliency and
Recovery of AWS
• Simulate failures of
instance of service
• Shutting down one or
more of VMs

46. 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

48. https://martinfowler.com/articles/microservice-trade-offs.html

50. Microservices Concerns

56. Fast, agile, inexpensive, and massively scalable infrastructure,
offered fully self-service and with pay-as-you-go billing

57. 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

58. Container Platform
Container Dashboard
Docker Universal
Control Plane
Container
Orchestration
Container Engine
Operating System Linux, [windows] Linux, [windows] Linux

60. 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

62. Too stressed
Processor,
Memory &
Network
Too many noisy
microservices
neighbors
Can handle
more
microservices
Cluster's automatic Resource-Balancing in Service Fabric
VM crashes!!

64. Developing a single application as a suite of small services