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, […]
In this episode, we conclude our three part series on Service Tiers, and how they can be used to prevent disasters in applications using service based architectures. We also take a look at the very first AWS service. Any guess what that service is? Finally, what does redundancy look like in outer space? And just […]
On January 21, 2020, Amazon announced a reduction in the cost of their Elastic Kubernetes Service. The cost to run a cluster in EKS went from 20c per hour to 10c per hour. It’s important to note that this only impacts the overhead necessary to run a single cluster. This means the per month cost […]
In this episode, we continue our three part series on Service Tiers, and how they can be used to prevent disasters in applications using service based architectures. We also take another look at Amazon S3, and ask the question, how large is S3? The answer might surprise you. All of this, in this episode of […]
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. Service Tiers are […]
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 […]
Five guiding principles for building, managing, monitoring, and maintaining state-of-the-art web applications by: Lee Atchison Modern web applications have a lot riding on them. Our customers depend on them, and our business depends on them. Without modern web applications, many businesses would not survive. Modern web applications must scale to our biggest needs without suffering […]
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 […]