Tim Gross introduces the Autopilot Pattern with illustrated examples and a walkthrough of our Autopilot Pattern example application
Joyent celebrates open source DC/OS container orchestration.
Using `docker logs` to get our container logs works in development but in production we need to centralize our logs. Triton has support for the syslog, Graylog, and Fluentd log drivers and we can use them to support production-ready log collection.
Deploying containerized applications and connecting them together is a challenge because it forces developers to design for operationalization. Autopiloting applications are a powerful design pattern to solving these problems. By pushing the responsibility for understanding startup, shutdown, scaling, and recovery from failure into the application, we can build intelligent architectures that minimize human intervention in operation. But we can't rewrite all our applications at once, so we need a way to build application containers that can knit together legacy and greenfield applications alike. This project demonstrates the autopilot pattern by applying it to a simple microservices deployment using Nginx and two Node.js applications.
Joyent has been running Node.js in production and at scale for over 5 years. As such, we've learned production practices for designing, deploying and debugging Node.js apps and we've built container-native solutions to optimize app performance, security, and management. Experience the container-native difference!
Get an introduction to Containerbuddy, a scheduler agnostic and vendor-neutral tool that simplifies the process for containerizing applications by doing the things most existing apps don’t:
This post demonstrates how you can deploy and scale a Node.js application backed by Couchbase and load balanced with Nginx. All the components are running in multiple Docker containers on Triton, and use Containerbuddy to automate discovery and configuration. We're using Docker Compose to deploy the application and scale it across the data center on Triton.
In a container-native project, we need to balance the desire for ephemeral infrastructure with the requirement to provide a predictable load-balanced interface with the outside world. By updating DNS records for a domain based on changes in the discovery service, we can make sure our users can reach the load-balancer for our project at all times.
Container-native applications have new responsibilities for discovery. But no one wants to rewrite all our current applications! So what do we do about it?
Containerbuddy simplifies service discovery in Docker and provides a workaround for applications not designed from the start for container-native discovery. Here I demonstrate how to make Nginx container-native with Containerbuddy.
Joyent CTO, Bryan Cantrill, sits down with Couchbase’s Traun Leyden to understand why the team at Couchbase is so excited about the Triton elastic container service and how you can easily use Triton to spin up a Couchbase cluster within minutes.
The Triton Elastic Container Infrastructure (formerly SmartDataCenter or SDC7) that powers Joyent's public cloud is open source and available for anybody to install to power private clouds, allowing users to enjoy the same platform everywhere.
DevOps expert Casey Bisson demonstrates the process of scaling a Docker deployment from a laptop to the cloud.
DevOps expert Casey Bisson presents the advantages of running your apps on container-native infrastructure, instead of in VMs.
In this talk, Bryan Cantrill, CTO of Joyent, describes the debugging techniques Joyent has employed across a multitude of customers.