Think differently, think microservices
As we move from Service-Oriented Architecture (SOA) to microservice architecture, JP Morgenthal (CTO, Application Services at DXC.Technolgy) believes most industries are not taking full advantage of this distinctive method of developing software has to offer.
For many developers, enterprise applications are best built using micro services due to its scalability. It uses many coding philosophies like Conway's Law and Brooke’s law to guide more efficient development mindsets.
Many large scale web based companies like Amazon, eBay and Netflix have evolved from monolithic to microservices architecture. But JP believes micro services have still not been widely adopted: “The barriers for adopting microservices as an organisational program are often tied to how IT is organised as well as the limited resources for skilled architects in this area.|” he said.
“I would say in most industries there are extremely immature efforts. There is some great opportunities around standardising within the industry around a business context. However, most businesses have not figured out what their individual business contexts should be.”
The first steps to develop this technology is to understand he significance of macro vs micro perspective of microservices. “The macro view is about the program that the business puts in place to ensure that all development is following the same rules for creation and design of microservices. The micro view focuses on the characteristics for designing a single microservice.” said JP.
The possibilities of micro services are limitless. While liberating for an enterprise, this can cause headaches on how its developed. JP believes: “The goal should be to align to business contexts, but there are many ways to view a business, such as customer, operational, executive, etc. If you're using this a means of organising your microservices then you will arrive at very different architectures.”
Speed and costs
Where will microservices move over the next few years? “many will jump on the microservices bandwagon, but will not really put the effort behind adhering the key principles and characteristics necessary to get the key value behind moving to this type of program. This will result in the typical trough of disillusionment.” says JP.
Micro services go well beyond APIs, instead having the potential to decompose a business problem into well-defined business capabilities. “The continued drive for speed and costs required to compete in a digitally transformed world will force businesses to press on to get this right,” JP concluded.
Performing his speaker session ‘Thinking micro services’ at SDxE next month, JP Morgenthal will offer the audience a better understanding of the emerging technology.
The audience will take away:
1. An understanding of the mindset required to design microservices.
2. The ways that moving to microservices changes how IT operates and manages applications
3. What are the macro and micro perspectives regarding a microservices program