Everything comes in cycles. Back in 2005 we discussed, defined and developed service orientated architecture (SOA) based solutions  .Today,when asked what the best-in-class software blueprint is, we tend to refer to microservices .
Behind both terms sits the same, simple concept – to develop and design independent, “utility based” services that can drive and provide flexibility, security and agility .
We are moving from the 2nd to the 3rd platform (the 1st refers to the mainframe era (monolithic), the 2nd refers to client-server based computing and the 3rd is the web native landscape where users have access to apps and data from everywhere at any time with any device). More and more organisations are moving into a digital landscape where applications, data and automation are king.
Introduced 10 years ago, microservices are one way to design and build applications. Both a monolithic and/or SOA based approach is and will still be a valid option. However, the application of microservices based design is on the increase, in particular for organizations that make use of 3rd platform based capabilities.
Microservices demand a new way of constructing Infrastructure capabilities – Microservices-aware Infrastructure has to follow a Lego®-Brick approach. The resulting infrastructure platform will have to be fully software based. This implies that control of the data center is fully automated by software so that hardware configuration, storage provisioning and network configuration are managed through software. This is in contrast to traditional data centers, where the infrastructure is typically defined by hardware and devices.
To achieve full digital maturity, and to accelerate the digital journey, an organisation’s infrastructure landscape has to conform to a clear set of design patterns – for example, ease of use, self-service, agility and flexibility. However, it can be tricky to navigate around all the terms involved, so to provide some guidance on microservices, we published today a document with two main intentions: To provide a detailed view of the impact microservices is having on infrastructure; and to examine how today’s infrastructure should be designed to support microservices.
See here the link to the 14-page POV.
 See Capgemini’s SOA (Service Orientated Architecture) point of view papers as well as whitepapers [1,2] were we outlined the notion of “everything as a service” in 2005.
 The term “microservice” was discussed at a workshop of software architects near Venice in May, 2011