Chris Richardson(@crichardson) 's Twitter Profileg
Chris Richardson

@crichardson

Learn-Build-Assess: https://t.co/rXmFfuwqJe, transactional microservices. https://t.co/MyA2SnQxqI patterns. Author of Microservices Patterns. Frameworks. Consulting

ID:14262063

linkhttp://www.chrisrichardson.net/about.html calendar_today31-03-2008 00:12:25

12,5K Tweets

16,4K Followers

1,0K Following

Follow People
Chris Richardson(@crichardson) 's Twitter Profile Photo

Just remember: there is not such thing as a microservice.

The microservice architecture is an architectural style that structures an application (a.k.a. system) as a set of loosely coupled services.

account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

I recently read the new Enterprise Technology Leadership Summit book by Demingā€™s Journey to Profound Knowledge by John Willis and Derek Lewis. It was a fascinating worthwhile read. I highly recommend it.

itrevolution.com/product/demingā€¦

I recently read the new @ITRevSummit book by Demingā€™s Journey to Profound Knowledge by John Willis and Derek Lewis. It was a fascinating worthwhile read. I highly recommend it. itrevolution.com/product/demingā€¦
account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

Let's imagine that your developing a microservices-based application and you need to implement a major new feature. For example, you want to implement coupons:

Let's imagine that your developing a microservices-based application and you need to implement a major new feature. For example, you want to implement coupons:
account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

I recently read the new Enterprise Technology Leadership Summit book by Demingā€™s Journey to Profound Knowledge by John Willis and Derek Lewis. It was a fascinating worthwhile read. I highly recommend it.

itrevolution.com/product/demingā€¦

I recently read the new @ITRevSummit book by Demingā€™s Journey to Profound Knowledge by John Willis and Derek Lewis. It was a fascinating worthwhile read. I highly recommend it. itrevolution.com/product/demingā€¦
account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

I've written another article about using service blueprints to clarify architecture.

It describes how a service blueprint can visualize a user scenario, the system operations that support the scenario and the entities (a.k.a. DDD aggregates) that the system operations act upon.

I've written another article about using service blueprints to clarify architecture. It describes how a service blueprint can visualize a user scenario, the system operations that support the scenario and the entities (a.k.a. DDD aggregates) that the system operations act upon.
account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

The essence of applying the Microservice architecture pattern is defining the service architecture: identifying the services, defining their responsibilities, their APIs and their collaborations (with other services).

The essence of applying the Microservice architecture pattern is defining the service architecture: identifying the services, defining their responsibilities, their APIs and their collaborations (with other services).
account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

Key lessons:

1. Be very, very careful when using shared libraries that contains 'unstable business rules' in a microservice architecture.
2. More generally ensure your services encapsulate change rather than having changes regularly impact multiple services

1/n

account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

One key dark energy force that shapes an architecture is team autonomy.

Team autonomy is the ability of a team to make decisions and take actions without the need for approval from other teams.

It's critically important for rapid, frequent, and reliable software delivery

One key dark energy force that shapes an architecture is team autonomy. Team autonomy is the ability of a team to make decisions and take actions without the need for approval from other teams. It's critically important for rapid, frequent, and reliable software delivery
account_circle
Chris Richardson(@crichardson) 's Twitter Profile Photo

Stumbled across this 2017 article from Gregor Hohpe about improving vocabulary (and behavior):

Replace: Alignment with Doing

Replace: Failure Culture with Learning Culture - my favorite

Add: Value

linkedin.com/pulse/you-wantā€¦

account_circle