Interested in making the switch to microservices but thinking it’s too good to be true? Or you have already made the switch but you’ve started to notice that local development is harder than it used to be? You’re not alone.
Learn how Cloud-Native kills developer productivity and why the benefits of switching to microservices and containers may be the root cause of a more serious challenge you’ll face down the road.
This paper dissects the biggest pain point of Cloud-Native: complexity for developers.
Recent years have witnessed a continuing trend toward the adoption of microservices and Cloud-Native technologies. This shift involves a gradual de-emphasis of monolithic virtual machines in favor of microservices, containers, and related technologies.
The technologies that make microservices powerful in production have made the development experience worse.
This shift has good reasons behind it: microservices simplify collaboration across teams while containers enable automation of tedious testing, deploys, and other ops tasks. While these advantages are significant enough to have caused the shift toward Cloud-Native in the first place, they are not without costs.
The technologies that make microservices powerful in production have made the development experience worse. Relatively simple tasks, like running code locally to test, now require significant time and effort. These inefficiencies add up when repeated across large teams with engineers that have varying DevOps skill levels. The introduction of microservices presents serious new challenges for developers. Engineering teams, whether they realize it or not, must solve this problem when they adopt microservices.