Álvaro HernándezGuest
Nikolay SamokhvalovHost
Michael ChristofidesHostWhy are you talking about Citus at all? Citus is in the hands of Microsoft.
What happened here? You developed Stargress, and then somehow these paths joined, right? They met these things, and you have examples.
That's why you mentioned these two petabyte examples, right? Can you explain a little bit what's happening, why you focus on Cytos so much lately?

I see a growing concern and needs to scale Postgres beyond the single primary for the reasons I mentioned before.

And that's why we are also seeing an explosion of new sharding technologies for Postgres.

We are seeing a lot of people coming to us asking how we can shard our database.

And so we saw this need and we saw early that we had to provide users a way to share.

And actually we were in a very privileged position, I would say, because What we've done in Stackers with single clusters is orchestrate and allow you to run the whole stack of components that you need to run Postgres, connection pooling, backups, monitoring, all that, all automated and all packaged.

So deploying it is extremely easy while also following best practices that we have from our company's operational experience.

But then we saw that creating a siteless cluster involved a lot of manual work because it's no longer one cluster.

Now, if you think about it and the model we follow in StackRes is that every component of the siteless cluster, the workers, the coordinator, all of those are a Postgres cluster in itself.

typically with more than one instance also for high availability purpose, right? And they need to be wired up precisely with the same configuration parameters across many places or otherwise it will not behave as a single cluster.

So it's not only a lot of work to wire up as let's say a 24, 48 node Citrus cluster, but also to do it right.

And with our automation and orchestration that we built for StackRes, we could do this work.

And now the reality is that if you use a StackRes and want to create a sharded cluster with Citus, by the way, we support all the other sharding technologies in StackRes, not only Citus, even though it's the most used and the most feature complete, I would say, solution for sharding that we have.

But with the 13 lines of Jaml, really high level, you can create a side of cluster of 60 nodes in a few minutes.
Why are you talking about Citus at all? Citus is in the hands of Microsoft.
What happened here? You developed Stargress, and then somehow these paths joined, right? They met these things, and you have examples.
That's why you mentioned these two petabyte examples, right? Can you explain a little bit what's happening, why you focus on Cytos so much lately?

I see a growing concern and needs to scale Postgres beyond the single primary for the reasons I mentioned before.

And that's why we are also seeing an explosion of new sharding technologies for Postgres.

We are seeing a lot of people coming to us asking how we can shard our database.

And so we saw this need and we saw early that we had to provide users a way to share.

And actually we were in a very privileged position, I would say, because What we've done in Stackers with single clusters is orchestrate and allow you to run the whole stack of components that you need to run Postgres, connection pooling, backups, monitoring, all that, all automated and all packaged.

So deploying it is extremely easy while also following best practices that we have from our company's operational experience.

But then we saw that creating a siteless cluster involved a lot of manual work because it's no longer one cluster.

Now, if you think about it and the model we follow in StackRes is that every component of the siteless cluster, the workers, the coordinator, all of those are a Postgres cluster in itself.

typically with more than one instance also for high availability purpose, right? And they need to be wired up precisely with the same configuration parameters across many places or otherwise it will not behave as a single cluster.

So it's not only a lot of work to wire up as let's say a 24, 48 node Citrus cluster, but also to do it right.

And with our automation and orchestration that we built for StackRes, we could do this work.

And now the reality is that if you use a StackRes and want to create a sharded cluster with Citus, by the way, we support all the other sharding technologies in StackRes, not only Citus, even though it's the most used and the most feature complete, I would say, solution for sharding that we have.

But with the 13 lines of Jaml, really high level, you can create a side of cluster of 60 nodes in a few minutes.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.