Microservices and Cloud-Native Applications — Where We are and What Lies Ahead
There are two paths to choose from in the transformation to microservices and cloud-native apps that have equal appeal depending on your starting point. One path is for existing applications, which will be well served by the service-mesh style ecosystem. The other path — primarily for new applications — will be based on deploying new programming models and technologies, like Reactive Systems and RSocket.
We will see these exist side-by-side within the same organizations for the foreseeable future. The thing to get right is finding the best way to bridge between these two paths and evolve at the right pace based on your needs. There are lots of good reasons for transitioning to microservices and cloud-native applications with lots of interest in getting there. At this early stage, how you get there is not set in stone.
Microservices and Cloud-Native: 2 Paths to Get There - Container Journal
Microservices and cloud-native development promise agility, resilience, organizational alignment and improved…
I wrote a full-length article for Container Journal that looks at the reasons why this two-pronged attack is a sensible approach for getting us to microservices and cloud-native applications.
At Netifi, we’re working hard building tools and technology to arm developers and decision makers with the building blocks for this transition. Our objective remains making your journey easier no matter which of the two paths you are on.