As a technology leader in your organization, many of your decisions come down to allocating resources: balancing and prioritizing risk and reward, stability and velocity, the present and the future. In an ideal world, technical debt would always be addressed before it started accruing interest. Long-term maintenance and operations expenses would be accurately weighed against the short-term development expenses that could mitigate them.
Migrating your database from an on-premise server to an AWS Relational Database Service (RDS) instance can be a daunting task. Moving a production database with continually changing data requires plenty of effort - especially if you’re also switching database engines.
Charity Majors, co-author of Database Reliability Engineering, shared a tweet that drives home how to approach the transition from single applications to a complex, distributed system of microservices.
@mipsytipsy. “Embrace the fact that everything is failing all the time - and it’s okay! We build for resiliency, not uptime.” Charity Majors, Twitter, https://twitter.com/mipsytipsy/status/1134499865335963648.
You can invest a lot in making any single system component reliable, performant, and scalable. The investment is often worthwhile and necessary, but what matters to users is the system’s uptime as a whole. Reliable components aren’t enough to make the entire system reliable if it’s unable to tolerate and recover from failures. Here are some thoughts about building your system for resiliency and two popular microservices patterns to cope with failure.
Containers are increasingly becoming the de-facto strategy for cloud native deployments. With the question of orchestration looming over those deployments, cloud vendors continue to provide multiple offerings for managing your containerized services. In this article, we’ll compare 3 main Azure offerings for container orchestration: Azure Web Apps, Azure Container Instances, and Azure Kubernetes Service.
Organizations across all industries are reaping the benefits of powering their business solutions in the cloud. However, selecting a provider for your cloud-native applications can be a tough decision. There are many options to choose from that have a variety of managed services to help you successfully transition to a cloud-native architecture. In this article, we explore three reasons why Microsoft Azure is one of the most popular options for hosting your application in the cloud.