Microservices are the hot new thing, but where did they come from, and where are they going?
This keynote will take you through the many origins of microservices. In it I’ll share with you some of the surprising influences and prior art that have shaped what they have become.
By understanding where microservices architectures have their roots, we can learn from the past and avoid making the same mistakes – and we can also start to see where microservices will be going next.
This talk was delivered as the keynote at QCon Sao Paulo in 2015.
28. @samnewman
“Netflix embraces Service Oriented Architecture
(SOA) composed of many small fine grained
services that do one thing and one thing well.”
http://techblog.netflix.com/2015/02/whats-trending-on-netflix.html
47. @samnewman
“(i) Make each program do one thing well.
To do a new job, build afresh rather than
complicate old programs by adding new
features.”
48. @samnewman
“(i) Expect the output of every program to
become the input to another, as yet
unknown, program. Don't clutter output
with extraneous information. Avoid
stringently columnar or binary input
formats. Don't insist on interactive input..”
49. @samnewman
“(iii) Design and build software, even
operating systems, to be tried early, ideally
within weeks. Don't hesitate to throw away
the clumsy parts and rebuild them.”
51. @samnewman
1972
“This paper discusses modularisation as a
mechanism for improving the flexibility and
comprehensibility of a system while allowing
the shortening of its development time"