Nikita Shamgunov
👤 PersonAppearances Over Time
Podcast Appearances
And of course, that statement, the team you build is the company you build, can be applied at every stage of the company. And so this year, the team you build is the company you build was applied to the management team. So we have now a fantastic staff team, VP of engineering coming from Mongo, VP of product coming from GitHub.
And of course, that statement, the team you build is the company you build, can be applied at every stage of the company. And so this year, the team you build is the company you build was applied to the management team. So we have now a fantastic staff team, VP of engineering coming from Mongo, VP of product coming from GitHub.
So we apply this team you build, the company you build, to each iteration. And the year 25 is going to be about GenAI, and then we're bringing some of the AI talents to the team as well.
So we apply this team you build, the company you build, to each iteration. And the year 25 is going to be about GenAI, and then we're bringing some of the AI talents to the team as well.
So we apply this team you build, the company you build, to each iteration. And the year 25 is going to be about GenAI, and then we're bringing some of the AI talents to the team as well.
The original idea was to build an open source alternative to a very popular product called AWS Aurora. The key idea of Aurora, which we took to the next level, was separation of storage and compute. What you do is you build kind of one storage for everyone. And what I mean by that is it's one global multi-tenant storage system.
The original idea was to build an open source alternative to a very popular product called AWS Aurora. The key idea of Aurora, which we took to the next level, was separation of storage and compute. What you do is you build kind of one storage for everyone. And what I mean by that is it's one global multi-tenant storage system.
The original idea was to build an open source alternative to a very popular product called AWS Aurora. The key idea of Aurora, which we took to the next level, was separation of storage and compute. What you do is you build kind of one storage for everyone. And what I mean by that is it's one global multi-tenant storage system.
Compute is still good old compute of a virtual machine in which Postgres lives and then attaches to your storage. So the first version of that was built in about 12 months. And then in a year, we were ready and we started to onboard some internal users. And then we started working on the launch process. As we started to work on the launch, it leaked, right?
Compute is still good old compute of a virtual machine in which Postgres lives and then attaches to your storage. So the first version of that was built in about 12 months. And then in a year, we were ready and we started to onboard some internal users. And then we started working on the launch process. As we started to work on the launch, it leaked, right?
Compute is still good old compute of a virtual machine in which Postgres lives and then attaches to your storage. So the first version of that was built in about 12 months. And then in a year, we were ready and we started to onboard some internal users. And then we started working on the launch process. As we started to work on the launch, it leaked, right?
Because we didn't hide the website behind a password. So suddenly posted it in Hacker News and we had a big discussion on Hacker News as well as a lot of traffic coming to the website. And then we also, right before that, we started to see our GitHub repo and we were building in the public, the stars started to go vertical. And we're like, wow, what's going on?
Because we didn't hide the website behind a password. So suddenly posted it in Hacker News and we had a big discussion on Hacker News as well as a lot of traffic coming to the website. And then we also, right before that, we started to see our GitHub repo and we were building in the public, the stars started to go vertical. And we're like, wow, what's going on?
Because we didn't hide the website behind a password. So suddenly posted it in Hacker News and we had a big discussion on Hacker News as well as a lot of traffic coming to the website. And then we also, right before that, we started to see our GitHub repo and we were building in the public, the stars started to go vertical. And we're like, wow, what's going on?
We started to get validation that we're onto something. And the GitHub repo was, again, public. And the description in the repo was, this is an open source alternative to AWS Aurora. And there was high velocity on the repo, right? So we were shipping a lot of code.
We started to get validation that we're onto something. And the GitHub repo was, again, public. And the description in the repo was, this is an open source alternative to AWS Aurora. And there was high velocity on the repo, right? So we were shipping a lot of code.
We started to get validation that we're onto something. And the GitHub repo was, again, public. And the description in the repo was, this is an open source alternative to AWS Aurora. And there was high velocity on the repo, right? So we were shipping a lot of code.
The tools that we used also helped both from the standpoint of how fast we can build hardcore foundational technology and from the marketing standpoint as well to believe it or not. So our storage is written in Rust and GitHub has this viral loops that's called GitHub trending that are on a per language basis.
The tools that we used also helped both from the standpoint of how fast we can build hardcore foundational technology and from the marketing standpoint as well to believe it or not. So our storage is written in Rust and GitHub has this viral loops that's called GitHub trending that are on a per language basis.
The tools that we used also helped both from the standpoint of how fast we can build hardcore foundational technology and from the marketing standpoint as well to believe it or not. So our storage is written in Rust and GitHub has this viral loops that's called GitHub trending that are on a per language basis.