I’m often asked for a list of articles, videos, presentations, interviews, or podcast episodes that I have made on a particular topic. I get this request for a wide variety of topics around cloud computing, DevOps, digital applications, and application modernization. Usually, I can create a list of 8-20 links to things I’ve written, created, […]
Welcome to the inaugural episode of Modern Digital Applications! I hope you’ll find this podcast informative and helpful. My goal is to try and keep the episodes short, so that they can be consumed during a single morning average commute trip to work. This episode is only 11 minutes long. Please, let me know how […]
It’s simple, really — services call other services and they take actions based on the responses from those services. Sometimes, that action is a success, sometimes it’s a failure. But whether it is a success or a failure depends on if the interaction meets certain requirements. In particular, the response must be predictable, understandable and reasonable for the given situation. This is important so that the service reading the response can make appropriate decisions and not propagate garbage results. When a service gets a response it does not understand, it can take actions based on the garbage response and those actions can have dangerous side effects to your service and your application.
Bringing down an entire application is easy. All it takes is the failure of a single service and the entire set of services that make up the application can come crashing down like a house of cards. Just one minor error from a non-critical service can be disastrous to the entire application. There are, of course, many ways to prevent dependent services from failing. However, adding extra resiliency in non-critical services also adds complexity and cost, and sometimes it is not needed. Read the entire article today in The New Stack.
Microservices is a hot topic in software development circles these days. And for some very good reasons. Put simply, the traditional way of building enterprise applications—using a monolithic approach—has become problematic as applications get larger and more complex. So developers are turning to a microservices software development architecture, in which applications are structured as collections […]
This is the second part of a two part series on microservice architectures, how they are used in application development and the role that APIs play within them. • Click here to go to article •
This is the first part of a two part series on microservice architectures, how they are used in application development and the role that APIs play within them. The second part looks at what distinguishes a typical Web API that you might add to your enterprise from a microservice (with an API) and when the […]
Take a look at the article Microservice Architectures: What They Are and Why You Should Use Them>, written by me and published by New Relic. This is an update and extension to the article “Why Use Microservices?” written by me previously on this blog.
It’s an increasingly common scenario: As a company grows, it finds that it needs to move away from the monolithic software architecture that powered its initial success. The alternative? A microservices approach that provides more speed and flexibility. That’s the story told by both our guests on the latest episode of The New Stack @ […]