Watch the screencast and learn how to install the Triton CLI tool and use CloudAPI to manage containers, VMs, networks, and storage in Triton data centers.
It's been said that we don't really understand a system until we understand how it fails. Despite having written a (toy) TCP implementation in college and then working for several years in industry, I'm continuing to learn more deeply how TCP works — and how it fails. What's been most surprising is how basic some of these failures are. They're not at all obscure. I'm presenting them here as puzzlers, in the fashion of Car Talk and the old Java puzzlers. Like the best of those puzzlers, these are questions that are very simple to articulate, but the solutions are often surprising. And rather than focusing on arcane details, they hopefully elucidate some deep principles about how TCP works.
Watch the screencast of how to install Docker, dockerize an app, and run it in production on Triton Cloud
Join me, a front-end dev and new Docs Editor for Joyent, while I dockerize my first app and then run it in production on Triton Cloud.
Applications developed with the Autopilot Pattern have containers acting as autonomous actors using an external service catalog like Consul or etcd for coordination. Both services bring assumptions that bring challenges to serverless environments.
Something that got a little lost in the excitement of Samsung’s recent acquisition of Joyent was dtrace.conf(16), our quadrennial (!) unconference on DTrace. The videos are up, and in the spirit of Adam Leventhal‘s excellent wrap-ups from dtrace.conf(08) and dtrace.conf(12), I wanted to provide a survey of the one-day conference and its content.
Persistent storage in Docker is a stumbling block for many production deployments, but the problem is easier to solve than you might imagine, and we can do it with the infrastructure and apps we already use and depend on.
Tim Gross introduces the Autopilot Pattern with illustrated examples and a walkthrough of our Autopilot Pattern example application
You may have seen that Samsung is acquiring Joyent. One of the quirks about acquisition announcements is that for any company with even a modest number of shareholders (be it private or public), there is a lag between when the acquisition is announced and when the acquisition actually closes — creating a peculiar time in which everything has changed and yet nothing has.
Let me not bury the lede: Samsung is acquiring Joyent, and Scott’s blog entry explains why we feel that this is such a good fit. As Joyent’s CTO, I wanted to offer my perspective and couch this acquisition in its broader historical context: the world’s largest consumer electronics company is acquiring a cloud computing pioneer; what’s going on here?
Since its inception, just over ten years ago, Joyent has lived on the leading edge of technical innovation. The Joyent team pioneered public cloud computing (and hybrid cloud), nurtured and grew Node.js into a de facto standard for web, mobile and IoT architectures, and was among the first to embrace and industrialize containers, compute-centric object storage, and what is now coming to be known as serverless computing.
We're always updating our documentation, but it's worth calling out some of the big changes, including the following recent updates to ContainerPilot, Triton CNS, CloudAPI, Triton CLI, and Docker.
Cisco's Mantl is intended to be a standardized platform for containerized microservices. It packages a number of open source components with a single install process. Joyent Triton, including our public cloud and private data centers world wide, is now an officially documented platform for Mantl.
Container scheduling and orchestration are among the most critical problems to solve in modern applications, but it turns out they're not so tough if you look at them the right way.
Joyent lowers pricing for container-native computing and demonstrates the advantages of running containers securely on bare metal with new instance packages designed for every workload.