The latest News and Information on DevOps, CI/CD, Automation and related technologies.
For many software engineers and developers, using standard libraries or built-in objects is just not enough. To save time and increase efficiency, most developers build on work done by others. Whatever the coding problem, there is likely another programmer who has already created a solution for it. There is usually no need to repeat the problem-solving process. This principle is known as Do not Repeat Yourself or DRY.
An on-call schedule tells you and everyone in the team who will be the first responder when an issue happens in production. The on-call team member is responsible for investigating the issue, either fixing the issue herself or adding other people who can help fix it. Having an on-call schedule is important for building reliable systems because making someone responsible for production issues makes sure that they're not ignored.
If your organization is planning to use AWS for deploying new releases, the deployment process can be tricky for teams outside of operations to learn and use, especially for those who don’t have expertise in the tooling to automate deployment. And, because there are several ways to deploy Kubernetes on AWS, including Amazon’s own EKS, understanding the different deployment options can be tough to navigate.
Kubernetes can bring a wide collection of advantages to a development organization, but efficiently deploying applications to Kubernetes is something many organizations are still working to perfect. Properly using Kubernetes can significantly improve productivity, empower you to better utilize your cloud spend, and improve application stability and reliability. On the flip side, if you are not properly leveraging Kubernetes, your would-be benefits become drawbacks.
Virtana recently published the results of a new State of Hybrid Cloud survey. One of the findings is that 81% of companies in the study who have started their migration to the public cloud have engaged multiple providers. This result tallies with a recent Gartner survey of public cloud users, in which 81% of those respondents said they are working with two or more providers.
I’ve learned a lot about serverless in my first full year at Stackery after joining from the Ops-focused automation company, Puppet. I’ve learned how to deploy rich CMS-backed web applications in a serverless way, how to cast incantations using CloudFormation’s intrinsic functions, but most of all I’ve learned that there’s a lot to learn in order to be successful in AWS.
Mutual of Enumclaw, a 100-year-old insurance company from Washington, modernized their policy processing system in order to reduce TCO and focus on their software and customers - not infrastructure. However, they realized serverless development still presents many DevOps challenges like environments, workflows, documentation and local development.
Azure Storage is like an all you can eat buffet, except the more you eat, the more you pay! This has provided organisations an almost limitless supply of storage, and as we all know, the more that’s available, the more we’ll use. Azure Storage has changed the way many organisations operate both in terms of availability and service.
