Rootconf proposals for round the year in 2018

On DevOps, security, cloud and IT infrastructure

Principles of Microservices

Submitted by Raghavendra Deshpande (@ragdeshp) on Monday, 5 March 2018

videocam_off

Technical level

Beginner

Section

Crisp Talk

Status

Submitted

Vote on this proposal

Login to vote

Total votes:  +1

Abstract

What are microservices? When should you use them? Should you start with microservices, or migrate to them over time?
Let us look into the Eight Key Principles for doing microservices well:

1) Model Around Your Business Domain: Domain-driven design can help you find stable, reusable boundaries
2) Build a Culture of Automation: More moving parts means automation is key
3) Hide Implementation Details: One of the pitfalls that distributed systems can often fall into is tightly coupling their services together
4) Embrace Decentralization: To achieve autonomy, push power out of the center, organizationally and architecturally
5) Deploy Independently: Perhaps the most important characteristic microservices need
6) Focus on Consumers First: As the creator of an API, make your service easy to consume
7) Isolate Failure: Microservice architecture doesn’t automatically make your systems more stable
8) Make Them Highly Observable: With many moving parts, understanding what is happening in your system can be challenging

Outline

What are microservices? When should you use them? Should you start with microservices, or migrate to them over time?
Let us look into the Eight Key Principles for doing microservices well:

1) Model Around Your Business Domain: Domain-driven design can help you find stable, reusable boundaries
2) Build a Culture of Automation: More moving parts means automation is key
3) Hide Implementation Details: One of the pitfalls that distributed systems can often fall into is tightly coupling their services together
4) Embrace Decentralization: To achieve autonomy, push power out of the center, organizationally and architecturally
5) Deploy Independently: Perhaps the most important characteristic microservices need
6) Focus on Consumers First: As the creator of an API, make your service easy to consume
7) Isolate Failure: Microservice architecture doesn’t automatically make your systems more stable
8) Make Them Highly Observable: With many moving parts, understanding what is happening in your system can be challenging

Speaker bio

Raghavendra Deshpande is currently working with IBM Digital Business Group as Developer Advocate – IBM Cloud and work with ISV’s, Partners, Startups Developer Community. He has 15 years of experience in development of enterprise level products and solutions with 10.5 years of service in IBM. Good knowledge of Social Enterprise Management, Telecom, Insurance, Banking, Logistic and Retail domains.

Comments

Login with Twitter or Google to leave a comment