Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Casey West
Using Docker in production
I recently sat down with Laura Frank, Docker captain and director of engineering at Codeship, to discuss the evolution of the Docker ecosystem and how it compares to other orchestration tools. Here are some highlights from our talk. Right now, Docker is an excellent tool to manage distributed applications. This is the result of quite a bit of evolution; in its earlier stages, Docker focused mainly on managing containers themselves.
Gary Sloper on the evolving role of DNS in building resilient infrastructure
Modern-day DNS goes beyond a simple internet “phone book” service to provide dynamic traffic management, flexibility, and performance. In this episode of the O’Reilly podcast, I had a chance to discuss modern-day DNS and its role in building resilient infrastructure with Gary Sloper, VP of global sales engineering at Dyn.
Why use Terraform?
Software isn’t done when the code is working on your computer. It’s not done when the tests pass. And it’s not done when someone gives you a "ship it" on a code review. Software isn’t done until you deliver it to the user. Software delivery consists of all the work you need to do to make the code available to a customer, such as running that code on production servers, making the code resilient to outages and traffic spikes, and protecting the code from attackers.
Optimizing app delivery with load balancers
Application delivery has evolved significantly in the cloud era. The industry has moved away from bulky servers hosting monolithic applications to thinly provisioned machines hosting applications that serve only a single purpose. Similarly, traditional approaches to resiliency, like failover and over provisioning, have given way to newer methods like load balancing and on-demand nodes.
Developer-defined application delivery
Cloud-native applications are designed to draw upon the performance, scalability, and reliability benefits of distributed systems. Unfortunately, distributed systems often come at the cost of added complexity. As individual components of your application are distributed across networks, and those networks have communication gaps or experience degraded performance, your distributed application components need to continue to function independently.
Achieving cloud-native operability with microservices, DevOps, and continuous delivery
Software developers like to make lists of three things and then say, smugly, “Pick any two.” For example, the Project Management triangle is good, fast, cheap (pick any two), and the CAP Theorem offers consistency, availability, and partition tolerance (pick any two). When working with cloud-native software, you don’t have the luxury of picking just two items from the trio of microservices, DevOps, and continuous delivery; you need all three.
The cloud-native future
Can you release new features to your customers every week? Every day? Every hour? Do new developers deploy code on their first day, or even during job interviews? Can you sleep soundly after a new hire’s deployment knowing your applications are all running perfectly fine?
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Casey
Contact Casey, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack