You’re adopting “DevOps” and “Microservices” because of the promise of delivering value faster to your users/customers. But you are not seeing the gains you want to see. You’ve got CI/CD/Pipelines/Tests/Microservices/etc. But you are still getting bogged down with teams being dependent on the progress of each other.
At this point, most developers know how to avoid the common mistakes when building APIs and integration code. Unfortunately, even as those developers make use of Retries, Idempotence, and Asynchronous Messaging, they often fall into a whole other set of problems that hurt their systems’ consistency, correctness, and maintainability.
This is the story of 30 microservices that resided in their own code repositories and that caused issues with code quality and developer productivity. It explains how to perform the Great Migration to the Monorepository and the ways in which it changed the software developers life for the better.
Sometimes software applications are behaving “normally” along strict definitions of HTTP statuses but under the surface, something is terribly wrong. In 2017, Checkr’s most important API endpoint went down for 12 hours without detection.
Learn how the New York Times learned to stop worrying and love serverless. Embracing serverless computing and working to advance the state of the art, The New York Times has empowered software developers to quickly launch stable, secure, and performant applications in an enterprise environment.
Microservice architecture and containerization have become the standards of modern application development. The challenges that developers face today are different from the problems that we used to solve earlier. Creators of the Java runtime respond to this with the appropriate functionality in the JDK. For example, an inexpensive cloud instance …
