At Joyent, we build open source software to automate data centers. Like Amazon, we operate our own public cloud. Unlike Amazon, we also offer the software that powers our public cloud to enterprises who want to run their own data centers. Simply put, we make it easy for companies to switch from the public cloud to a private data center, or to use both in a hybrid model. And, as I look across our customer base and sales pipeline, I see a clear trend toward a hybrid cloud model emerging among what I call “cloud mature” companies.
DevOps expert Casey Bisson answers your DevOps questions. Today's question: how can I successfully run my applications in multiple data centers?
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.
Enjoy bare metal performance with Joyent's latest releases of Node.js, MongoDB, PostgreSQL and Percona running container-native on Triton.
Triton CNS is a free, automated DNS solution that offers consistent and predictable addresses for changing infrastructure. Use Triton CNS as a free, high-performance alternative to virtual IPs and hosted load balancers.
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 ContainerPilot to automate discovery and configuration. We're using Docker Compose to deploy the application and scale it across the data center on Triton.
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.
Containerbuddy, the open source discovery and configuration helper for applications of all types, is now 1.0!
DBaaS solutions lock too many doors: we're locked into a service provider and locked out of configuring it as we need. Fortunately, modern operational patterns are emerging that eliminate the complexity of running even sophisticated applications like databases and free us from the lock-in of *aaS. Now we are free to develop on our laptops and deploy to private data centers, combining the simplicity we thought was only possible with *aaS with the portability of running applications on our own terms. Let's take a look at how to do that with MySQL.
Introducing the Triton command-line tool, complete with usage examples, configuration instructions, and rainbows.
Docker client applications can launch and control Docker containers across an entire Triton data center as a single Docker host. Learn how to get started in three steps.
Whether people feel that unikernels are wrong-headed and are looking for supporting detail or are unikernel proponents and want to know what the counter-arguments could possibly be, there is clearly a desire to hear the arguments against running unikernels in production.
Dave Jensen, Founder of Road Rules, explains why Road Rules selected Node.js and how they leverage the runtime for their innovative new app.
An unlikely pairing: Microsoft's CoreCLR and ASP.NET framework meet Joyent's secure bare-metal container hypervisor and debugging toolkit. See how you can leverage secure Linux containers in Triton to run CoreCLR apps in the cloud with bare metal performance.
At the beginning of the year, I laid down a few predictions. While I refuse on principle to engage in Stephen O'Grady-style self-flagellation, I do think it's worth revisiting the headliner prediction, namely that 2015 is the year of the container.