Smash Notes

Back to 272 - Anthony Eden, Founder of DNSimple, with Anthony Eden.

How Did DNSimple Let One Person Reach Many Accounts?

DNSimple bound each user to an account at the start. Login credentials were tied to billing and access control. Over the years the binding blocked new work, so DNSimple decoupled users from accounts into a many-to-many relationship. Many users can now belong to many accounts.

People use DNSimple for personal domains. The founder has domain names and also works on DNSimple domain names. DNSimple segments domains for set reasons: production domains sit in one highly restricted account, and other domains are experiments for fun. The founder says DNSimple might build a site or run something off an experimental domain without knowing whether it will live. A single user reaches each account under different access control. When a user was an account, separate access was impossible. The bigger application code gets, or the longer it lives, the harder a fundamental design decision becomes to change.

A business that must race toward the next round of funding, the next round of debt, a public listing, or the next revenue target will build around a core system instead of updating it. DNSimple never raised any funds, is profitable, and chose to change the core user-and-account relationship while still servicing customers.

Transcript

272 - Anthony Eden, Founder of DNSimple ·

From the transcript

And I think we've seen that internally in the N-Simple on a couple of concepts that we've changed over time. The, the most obvious one was some of our early implementations of users and accounts. So we bound everything together initially where a user was an account. So you logged in, and those credentials that you used were tied to things like billing and access control, right? And that, at first, that was fine, but over the years, that binding started to get more and more difficult to, it started blocking us from building new things.

And so One point we had to decouple those, and that's not an easy thing to do when you've built this stuff all throughout your application. But we managed to pull it off and got to the point where we now have a, a, a many-to-many relationship between users and accounts, so many users can be part of many different accounts, which I think is interesting because we have a lot of folks that use us for their personal domains, so I have domain names, but I also work on DNSimple's domain names.

See in transcript

Code with Jason

More from this episode

  1. How Did DNSimple Learn to Describe the Problem First?On the show, DNSimple has used the Shape Up process from Basecamp for a couple of years.
  2. Why Doesn't a Thousand-customer Plan Work for Ten Customers?On the show, scalability is kind of irrelevant in the beginning. The point is to get somebody and form a kernel of a user base.
  3. Why Does DNSimple Still Require a Credit Card?On the show, DNSimple never had a free tier.
  4. Why Does No Champion Force a Bigger Marketing Budget?A sale into an organization depends on a champion inside the business, even when the champion will not write the check.

People

More answers like this

The other side

More with Anthony Eden

Related episodes

Plays from this note through the rest of the episode.

Weekly highlights

One letter a week.

The notes worth hearing, with the minute they were said.