Microservices Design Patterns

functional decomposition or domain-driven design
well-defined interfaces
explicitly published interface
single responsibility principle
potentially polyglot

http://blog.arungupta.me/microservice-design-patterns/
http://blog.arungupta.me/microservices-monoliths-noops/
https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/
three-tier architecture — presentation, application, data
vs.
4 tier -- client, delivery, aggregation, services

Build software like you build houses

Interfaces facilitate visibility. Software is the only engineering practice that doesn't allow runtime visibility to end-user. If this were true for construction, it would mean your builder would have to live with you for you to even guess what the problem is. https://vimeo.com/221049715 https://github.com/stripe/veneur

Kafka messaging

https://kafka.apache.org/intro#kafka_mq and more generally https://kafka.apache.org/intro

yak butter recipe

Search This Blog