Menu
Sign In Search Podcasts Libraries Charts People & Topics Add Podcast API Blog Pricing

Neil Patel

๐Ÿ‘ค Speaker
1922 total appearances

Appearances Over Time

Podcast Appearances

And so initially, when we were trying to give it out to people, they were like, but I want to use this, but I don't have Elastic available right now, or I have to wait to get access to our companies or whatever. My co-founder, he was like, oh, no, I can just build something internally where we won't need to ask for anything just for them to try it out.

And so initially, when we were trying to give it out to people, they were like, but I want to use this, but I don't have Elastic available right now, or I have to wait to get access to our companies or whatever. My co-founder, he was like, oh, no, I can just build something internally where we won't need to ask for anything just for them to try it out.

And so initially, when we were trying to give it out to people, they were like, but I want to use this, but I don't have Elastic available right now, or I have to wait to get access to our companies or whatever. My co-founder, he was like, oh, no, I can just build something internally where we won't need to ask for anything just for them to try it out.

And so he made this thing called EventDB, which was just like this demo store inside of our product. And it was just meant to be like this easy onboarding for people who we just wanted feedback of, to be honest. The feedback was like, hey, this is really cool. The problem is, though, what you're trying to do, we just don't have enough data for it.

And so he made this thing called EventDB, which was just like this demo store inside of our product. And it was just meant to be like this easy onboarding for people who we just wanted feedback of, to be honest. The feedback was like, hey, this is really cool. The problem is, though, what you're trying to do, we just don't have enough data for it.

And so he made this thing called EventDB, which was just like this demo store inside of our product. And it was just meant to be like this easy onboarding for people who we just wanted feedback of, to be honest. The feedback was like, hey, this is really cool. The problem is, though, what you're trying to do, we just don't have enough data for it.

We want to do it, but we don't have enough data for what you're trying to achieve. And when we do all the costings and stuff, it's not going to work out for us to have enough to make the second part viable. And then you talk to them a little bit more and they say, but what are you using for your data store? How come I didn't have to connect you to anything?

We want to do it, but we don't have enough data for what you're trying to achieve. And when we do all the costings and stuff, it's not going to work out for us to have enough to make the second part viable. And then you talk to them a little bit more and they say, but what are you using for your data store? How come I didn't have to connect you to anything?

We want to do it, but we don't have enough data for what you're trying to achieve. And when we do all the costings and stuff, it's not going to work out for us to have enough to make the second part viable. And then you talk to them a little bit more and they say, but what are you using for your data store? How come I didn't have to connect you to anything?

Why am I sending everything and being able to read it back so easily? And then the penny dropped and we quickly realized that's the thing we should be working on first and make that viable. So that was the first MVP. It caused the pivot to happen within weeks, essentially, of us giving it to people to try out.

Why am I sending everything and being able to read it back so easily? And then the penny dropped and we quickly realized that's the thing we should be working on first and make that viable. So that was the first MVP. It caused the pivot to happen within weeks, essentially, of us giving it to people to try out.

Why am I sending everything and being able to read it back so easily? And then the penny dropped and we quickly realized that's the thing we should be working on first and make that viable. So that was the first MVP. It caused the pivot to happen within weeks, essentially, of us giving it to people to try out.

And then the second one was about actually 18 months after that when we released our beta cloud around our data store. So we took this demo data store and we made it real during that time. And so that was the second MAP.

And then the second one was about actually 18 months after that when we released our beta cloud around our data store. So we took this demo data store and we made it real during that time. And so that was the second MAP.

And then the second one was about actually 18 months after that when we released our beta cloud around our data store. So we took this demo data store and we made it real during that time. And so that was the second MAP.

It was interesting because you have already built a bunch of things up from the front end to API services back down to how those API services talk to a data store. So the new part was the data store. The old parts were the API server and the front end, which we were repurposing. The reality was the data store we were building was very novel in architecture.

It was interesting because you have already built a bunch of things up from the front end to API services back down to how those API services talk to a data store. So the new part was the data store. The old parts were the API server and the front end, which we were repurposing. The reality was the data store we were building was very novel in architecture.

It was interesting because you have already built a bunch of things up from the front end to API services back down to how those API services talk to a data store. So the new part was the data store. The old parts were the API server and the front end, which we were repurposing. The reality was the data store we were building was very novel in architecture.

And at the time, we felt like as long as we did these three things, we would have it done within a certain number of months, basically. And we were trying to go for the ingest will be brand new and we'll do it like this. Storage will only use object storage. Queries will only use serverless.

And at the time, we felt like as long as we did these three things, we would have it done within a certain number of months, basically. And we were trying to go for the ingest will be brand new and we'll do it like this. Storage will only use object storage. Queries will only use serverless.