Netflix, eBay, Amazon and the UK Government Digital Service have all used microservices.
The complexity can also have impacts on "network latency, fault tolerance, message serialization, unreliable networks, asynchronicity, versioning, varying loads within our application tiers etc," according to the article Microservices – Not a Free Lunch! by Benjamin Wootton, CTO of Contino.
He also wrote that there could be code duplication, asynchronicity between different microservices and that DevOps would be required for any microservices deployment.
The term first gained prominence in 2014.
Large-scale websites and applications that have evolved from monolithic architecture to microservices include Netflix, eBay, Amazon, the UK Government Digital Service, Real Estate, Property & Homes For Sale, Forward, Twitter, PayPal, Gilt, Bluemix, Soundcloud and the Guardian, according to Martin Fowler, Chief Scientist at ThoughtWorks.
In the early 2000s, Amazon transformed from the Obidos monolithic application to a service-oriented architecture which used encapsulated databases and smaller teams. While the company did not use the term ‘microservices’ to describe this, this has been a key case study for microservices.