Cloud infra, with Kurt Mackey (Fly.io) - S04E11

07/06/23 • 35 min

1 Listener

In this episode, we speak with Kurt Mackey, CEO of Fly.io. We discuss what it's like running physical servers in data centers around the world, why they didn't build on top of the cloud, and what the philosophy is behind the focus on pure compute, networking, and storage primitives. Kurt sheds light on the regions where Fly.io is most popular, why they’re adding GPUs, and the technology that makes it all work behind the scenes.

Hosted by David Mytton (Console) and Jean Yang (Akita Software).

Things mentioned:

ABOUT KURT MACKEY

Kurt Mackey is the CEO of Fly.io, a company that deploys app servers close to your users for running full-stack applications and databases all over the world without any DevOps. He began his career as a tech writer for Ars Technica and learned about databases while building a small retail PHP app. He went to Y Combinator in 2011 where he joined a company called MongoHQ (now Compose) that hosted Mongo databases which he sold to IBM, before turning his attention to building Fly.io.

Highlights:

[Kurt Mackey]: The original thesis for this company was there's not really any good CDNs for developers. If you could crack that, it'd be very cool. The first thing we needed was servers in a bunch of places and a way to route traffic to them. What we wanted was AnyCast, which is kind of a part of the core internet routing technology. What it does is it offloads getting a packet to probably the closest server, to the internet backbones almost. You couldn't actually do AnyCast on top of the public cloud at that point. I think you can on top of AWS now. So we were sort of forced to figure out how to get our IPs, we were sort of forced into physical servers for that reason. For a couple of years, it felt like we got deeply unlucky because we had to do physical servers. You’d talk to investors, and they'd be like, “Why aren’t you just running on the public cloud and then saving money later?” Then last year, that flipped. Now, we're very interesting because we don't run on the public clouds.

— [0:11:14 - 0:12:03]

[Kurt Mackey]: I think there's another thing that we've probably all reckoned with since 2011; a lot of the abstractions were wrong. As the front end got more powerful, I think we tried a lot of different things for— and what we ended up doing was inflicting this weird distributed systems problem on frontend developers. So I think that, in some ways, we just have the luxury of ignoring a lot of things that people have been trying to figure out for 10 years because we probably think that's wrong at this point. So we happen to be doing well at a time when server-side rendering is all the rage in a front-end community, which is perfect for us and nobody really cares about shipping static files around in the same way. I think it's just evolutionary. We kind of have a different idea of what's right now and can do simpler th...

Hosted by David Mytton (Console) and Jean Yang (Akita Software).

Things mentioned:

ABOUT KURT MACKEY

Highlights:

— [0:11:14 - 0:12:03]

Previous Episode

Serverless databases, with Monica Sarbu (Xata) - S04E10

In this episode, we speak with Monica Sarbu, CEO of Xata. We start with the philosophy behind serverless databases, why developers shouldn't need to think about relational databases, search, and analytics, whether the performance hit of accessing a database over HTTP matters, and how database branching works. She also talks about Xata’s plans for a global database, the company’s focus on UI developers, and what other databases are doing wrong.

Hosted by David Mytton (Console) and Jean Yang (Akita Software).

Things mentioned:

ABOUT MONICA SARBU:

Monica Sarbu is the Founder and CEO of Xata, a serverless database built for modern development. Prior to that, she worked on an open-source monitoring solution called Packetbeat which was acquired by Elastic in 2015. She is also the co-founder of tupu.io, a non-profit initiative that offers free mentorship to women, people of color, and other underrepresented groups in the tech industry.

Highlights:

[Monica Sarbu]: The idea of a single API is that because, like I said, this scenario happens in every company out there; when they start a new web application, they need to build this data platform internally. My thinking was why [does] every company out there need to reinvent the wheel when we can provide all this functionality: database, search functionality, analytics, time series data as well, and under a single API? This was the main purpose of having a single API.

— [0:05:14 - 0:05:49]

[Monica Sarbu]: I've seen that there are so many companies out there that are building their data platform on top of Airtable and they are developers. The reason behind that was that it's easier to use, and they had– While I was speaking with so many companies, I've seen so many hacks because they had hundreds of Airtables. They were synchronizing between them because you cannot really store a lot of data in one Airtable. My idea is — especially with serverless applications — that when you're building a web application, you have most of your logic in a lambda function so you cannot really use any of these databases and services that are out there, right? So Airtable was an easy-to-use approach but Airtable was not really meant to be built as a database. I've seen that there is a huge opportunity to build something that is as easy to use as Airtable but as scalable as a traditional database and also powerful as a traditional database.

— [0:25:12 - 0:26:16]

Let us know what you think on Twitter:

https://twitter.com/consoledotdev

https://twitter.com/davidmytton

Or by email: [email protected]

About Console

Console is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to.