Skip to main content

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

Comments

Post a Comment

Popular posts from this blog

Answer to interview question - "What is the most important thing Object Oriented languages have contributed to software development?" ...sufficiently  model  the real world and problem at hand before jumping the gun. ...the success of graphical user interfaces like X and Windows. A GUI consists of several objects which have a behaviour on their own, something that OO is able to represent closely. ...polymorphism to match the logical way classification worked in real life -> code reuse ..limit project churn s tackexchange Tony Hoare introduced Null references in ALGOL W back in 1965 “simply because it was so easy to implement”, says Mr. Hoare. He talks about that decision considering it “my billion-dollar mistake”.  http://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare
Post a Comment
Read more