Blog

I have long been a fan of RethinkDB, finding it to hit a sweet spot: developer friendliness (I <3 ReQL!) with Jepsen-grade robustness. This is the same ethos that we aspire to at Joyent, and that RethinkDB was born proprietary but later made open source made it feel like even more of a kindred spirit: I have leapt the chasm twice (first at Sun with what became illumos and then later at Joyent, where we open sourced our entire stack), so I felt I personally understood some of the arduous path that RethinkDB had walked.

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.

One of the exciting challenges of being an all open source company is figuring out how to get design conversations out of the lunch time discussion and the private IRC/Jabber/Slack channels and into the broader community.

Here in Silicon “blink and you might miss something” Valley, we spend a lot of time talking about the present and predicting the future, but not a whole lot of time reminiscing about the past. However, in honor of President’s Day this past Monday, we realized we might also benefit from learning a little bit about the present by revisiting history and reflecting on the past.

The event-oriented approach underlying Node.js enables significant concurrency using a deceptively simple programming model, which has been an important factor in Node's growing popularity for building large scale web services.

The performance of the file system, or disks, is often the target of blame, especially in multi-tenant cloud environments. At Joyent we deploy a public cloud on ZFS-based systems, and frequently investigate performance with a wide variety of applications in growing environments.

When your friends and family come to you with the flood of technology questions you’ve come accept as an occupational hazard, you know how to ask the critical, mission-saving questions such as, “is it plugged in” and “have you tried turning it on?”

Watch it Wednesdays are hand-picked videos from our Joyent engineers who have given talks in the past on a variety of open-source offerings. These videos have been selected for their ability to shed light on some of the most relevant, pressing topics in today’s developer community.

We’ve just updated Ubuntu 12.04 and Debian 6.0.6 to make Joyent an even sweeter ride for Linux users. Highlights of Joyent’s version 2.3.1 include Joyent GPG signed Debian and Ubuntu repos that offer secure Joyent updates and being able to set hostnames via CloudAPI using Mdata.

I have been thinking about this one for a while, because every now and again, mostly for testing purposes I find that I really wish I could reset a kstat. I have been able to figure out how to reset certain kstat(s) with MDB, but wondering if perhaps you have one method that makes it relatively easy to find and reset any kstat.

About

Support

Joyent.com Feedback

Thank You

Thank you for helping us improve joyent.com.

Forms are blocked

It appears you have an ad or script blocker that won't allow us to load our feedback form from app-sjf.marketo.com. To submit feedback, you can either temporarily unblock that domain, or email marketing@joyent.com. Email may take longer to get to the relevant people.