Microservices - An Architectural Pattern

20
Feb
2016

Microservices - An Architectural Pattern

Hype cycle

 

In the mid 2000s it was all about 'Services Oriented Architecture'. The hype machine is now squarely focused on microservices. SOA and microservices aim to solve two different problems, and as with most new architectural terms and patterns there is something good going on out there - it just takes a little digging to get to the good stuff.

Here are a few links on the topic...

1. Fowler is in on the game, defining the term, pattern, and approach with usual gusto.

http://martinfowler.com/articles/microservices.html

2. Here's an interesting article on building microservices using AWS Lambda - without servers.

https://aws.amazon.com/blogs/compute/microservices-without-the-servers/

3. Here's a great write up on the evolution of a framework from a tool to quickly build and test MVPs, into a fully-fledged microservices framework called Seneca.

http://www.richardrodger.com/seneca-microservices-nodejs

4. A few years ago now but still a good read from Netflix on Architectural Patterns for High Availablilty

http://www.slideshare.net/adrianco/architectures-for-high-availability-qconsf

(Image courtesy https://en.wikipedia.org/wiki/Hype_cycle)