I often hear a prospective client say: "With only 15 people, how can you deliver a good, fast, and reliable DevOps-as-a-Service solution for our organization?"
Sometime in the very near future, Docker is going to concede that Docker Swarm has lost and they'll have to yield the floor to Kubernetes.
Sarah Zelechoski provides hands-on instructions for standing up clusters, deploying a simple web application, and scaling your app properly.
I'll layout how you can make your developers badass with the power of Kubernetes and our DevOps-as-a-Service plan.
Michael Tuszynski, CTO at San Francisco-based Fandor, talks what it was like to implement RO’s DevOps-as-a-Service solution and what it’s like to work with us.
Is Kubernetes overkill? Most companies will decide to get off Heroku. The decision: choose a "simple" solution, or take a leap of faith and choose Kubernetes
Google is very invested in Kubernetes and is leaning heavily on their partners to help grow GCP. Our Google partnership brings major advantages to our clients
At ReactiveOps, our primary focus is to offer DevOps-as-a-Service. In addition to our monthly support offerings, we provide one-off Kubernetes consulting.
Since Google created Kubernetes, Google Container Engine (GKE) basically gives you a Kubernetes cluster out of the box. We'll look at kubernetes on GCP vs. AWS.
Kubernetes offers various types of volumes. The one that comes closest is the emptyDir. Kubernetes `emptyDir` is not the same as Docker's `--volumes-from`.
In this final post of this four-part series, I’ll focus on how you can tell if your organization is truly ready for a DevOps implementation.
DevOps implementation involves a dramatic cultural shift, including a willingness to adopt practices that facilitate the performance of lean product development
I’ll highlight some similarities between DevOps and Agile development, DevOps and (CI/CD), and some overall benefits of a DevOps implementation.
You’re ready to embrace DevOps. Or you’re in the midst of building a DevOps organization. Now what?
We open sourced Pentagon, our framework for building vanilla Kubernetes-based infrastructure in an opinionated way on AWS.
I’ve compiled some notes and thoughts on getting Logentries running in a Kubernetes environment.
In this edition of The New Stack Makers, Justin Mound and Eric Hole talk with Benjamin Ball about best practices that we perceive as emerging around Kubernetes
Scaling and automation only work when detailed monitoring is put in place. Monitored infrastructure is critical, but a lot of companies don’t make time for it.
Automated infrastructure is about saving time while having fewer dependencies. This post will cover: config management, deployment automation, and auto scaling.
Growth and business tides are key reasons why it’s important to scale infrastructure the right way. The goal is to make sure your infrastructure is flexible.
Whether or not root volumes on AWS need to be encrypted is a subject of debate. Since we use Ansible, we put together a role that creates an encrypted AMI.
Ansible’s simple requirements make it very easy to get started. But once you get a bit deeper some things might end up causing discomfort.
I want to share an example of an RO-style Kubernetes configuration on AWS with kops. It includes an undocumented feature that the community may find useful.
rok8s scripts are Kubernetes scripts that help manage the deployment of applications to Kubernetes via a continuous integration environment.
I’ll explain what Docker is, then walk through why it’s a beneficial tool to use for development and operations.
This post focusses on why using Docker is much less difficult than you might think and gives some basic commands and examples on how easy it is to use.
I recently took another look at Amazon Elastic Service. Some of these observations include supported versions, access controls and more dedicated master choices
How do you go about provisioning and deploying a production ready, highly available, Kubernetes cluster? The answer is kops.
Tools like Kubernetes enable seamless deployment and give teams a clear, real-time window into each other’s worlds.
Any sufficiently complicated cloud-based infrastructure contains an ad-hoc, informally specified, bug-ridden, slow (and more expensive) implementation of Heroku
Let’s take a deeper look at the top 4 concerns small to mid-sized SaaS, web and eCommerce companies have about outsourcing DevOps work.
High availability is the expectation that a system will operate continuously for a significant span of time.
AWS Lambda allows you to identify all of the failure or disaster situations that can occur (and their potential business impact) – in advance.
Development organizations are under pressure to release software at light speed. Exceptional application performance requires Dev insight and Ops weigh-in.
Identify what you want to protect, then create a disaster recovery plan that covers critical infrastructure and data– The Importance of cloud server backups.
DevOps-as-a-Service can be a real game changer. The right outsourced DevOps team can often help you achieve faster time to market and increased profitability.
When something goes wrong, monitoring and logging all the things will help you understand the data and troubleshoot the issue.
There comes a point where many organizations outgrow their one-size-fits-all PaaS. We recently completed a migration from Heroku to Kubernetes on AWS.
I’ve had my eye on Amazon’s Lambda and API Gateway services for a few months. This post walks through the setup along with the hitches I hit.
What DevOps means at ReactiveOps. Matt riffs on microservices, docker, AWS, and serverless architecture/AWS Lambda.