8 ms·
Landlord: Per-Tenant Stats in Postgres with Citus
- brightball 8y agoI wonder if/when Citus will have a GCP option?
- ddorian43 8y agoI wonder if/when they'll reoease multi-master ?
- craigkerstiens 8y agoWhen you say multi-master can you clarify a bit of what you're looking for? We have Citus MX which allows you to read and write from any node removing a coordinator as a bottleneck on any write throughput. Not sure if it would meet your needs or if you're looking to solve some other use case.
- ddorian43 8y agoYes, I meant mx.
- tpetry 8y agoThey seem to currently be to deep invested in the AWS architecture. But i am still waiting for Citus Cloud on GCP too.
- craigkerstiens 8y agoHi, Craig from Citus here. We're always continuing to explore other platforms beyond Citus Cloud on AWS. Stay tuned for the future as we'll add support for others. The input and feedback on which platforms people prefer is very helpful, so always feel free to drop us a note directly on that.
- brightball 8y agoGCP and Digital Ocean would be excellent. :)
- sam0x17 8y agoI also would be interested in GCP and digital ocean
- manigandham 8y ago+100 for GCP
- ci5er 8y agoWhy? Yes, AWS can be expensive for performance, but it scales well and is automatable. I 'get' why no Azure for greenfield, but why do you love GCP?
- thangngoc89 8y agowhen the rest of your infrastructure is already on GCP, running the database on the same cloud would reduce latency and bandwidth cost
- ci5er 8y agoWell, sure. I guess the broader question would be: Why use GCP? I like them well enough, but I find it easier to prototype on AWS. Why would a developer develop the MVP on GCP vs AWS and then go to scale there? (I realized that K8S has made this, recently, a moot point, and it comes down to cost ... but beside that is there anything?) EDIT: I realize that as a neo-Luddite, I just might be used to AWS, and would be open (mostly) to arguments to move to GCP if it is better (I'm not not talking about $/Gbps) EDIT2: As a (mostly) fan of Google - I probably would have gotten myself acclimatized to their platform if it was any good 10 years ago, but it wasn't, so I didn't, and I guess I'm asking: is there a good reason to learn how to switch?
- 8y ago
- jedberg 8y agoHeh I thought this was for landlords to track tenant data. I was excited for a second!
- mipmap04 8y agoJust curious - what sort of data would you want to track on tenants?
- dominotw 8y agoNoise levels would be good. When I am moving this noise is a total wildcard and luck. I would pay a premium to move in with less noise neighbours and possibly quite tenants can be rewarded with that premium.
- krisroadruck 8y agoI know I'd pay extra not to have to live next to neighbors with small children or yappy dogs. Still annoyed that it's illegal for there to be childless apartment communities.
- dragonwriter 8y ago> Still annoyed that it's illegal for there to be childless apartment communities. It's not, you are just probably not old enough for the ones that are legal.
- tpetry 8y agoWho doesn‘t love a session of bingo at the afternoom? :)
- jasonmp85 8y agoYou're in luck: you can! It's called buying a single-family detached home.
- danharaj 8y agoI respect Citus for the way they consistently praise the PostgreSQL community when promoting themselves.
- hemancuso 8y agoI’d love to know if anyone here has done a deep eval of Citus vs CockroachDB. They seem to be the two most promising solutions for horizontal scale-out Postgres and both are under very active development.
- qaq 8y ago?? outside of CockroachDB using PostgreSQL wire protocol they focus on very different use cases it seams. from CocroachDB website: "When is CockroachDB not a good choice? CockroachDB is not a good choice when very low latency reads and writes are critical; use an in-memory database instead. Also, CockroachDB is not yet suitable for: Heavy analytics / OLAP" I think Citus is actually very well suited for Heavy analytics / OLAP
- hemancuso 8y agoYes but they both target horizontial scale out and OLTP is a target for both. And yes, cockroach isn’t Postgres but it has SQL, versus something like Mongo or Cassandra.
- qaq 8y agoCitus claims OLTP but for a large cluster 2 phase commit is not a very viable approach.
- manigandham 8y agowhat do you mean?
- qaq 8y agoYou need all worker nodes to be available for 2pc to succeed. So the solution you have a standby for each node which is not very viable for a large cluster.
- 8y ago
- sam0x17 8y agoLove Citus's technology, but once again $99/month is ridiculous for a "dev" plan. Small startups want to use the same database from the pre-MVP dorm room phase all the way through their Series A, and while your technology would theoretically allow that, your pricing closes a lot of doors. No one wants to switch databases once their product is doing well enough to warrant $99/month for a database, so you are scaring away a lot of potential customers such as myself. Once again I implore you to consider adding a "starter" or "hobbyist" tier for $20/month or even $5/month. If you want to really be competitive, your product should be free to use until you have more than 200mb of data stored in your database, at which point usage-based pricing kicks in based off of the number of rows used.
- craigkerstiens 8y agoIt's helpful feedback, and something we'd love to work towards some day. The short of it is because of Citus architecture it does require multiple underlying nodes and there is some overhead that until you get to a larger scale Citus doesn't necessarily make sense. If you've only got 10 GB of data a single node instance on RDS should suit you just fine. We understand some of the costs of switching and have actively been working to build tools for you to plan to use something like Citus, but then migrate when the time comes. Libraries like activerecord-multi-tenant or django-multi-tenant ensure you're ready for Citus and work perfectly well on a single node Postgres database. Then when the time comes, which could be at $100 of RDS or $500 of RDS or larger, we have Citus warp [1] that allows you in a fully online way to replicate from RDS directly into a Citus cluster. Using it we've had customers with > 4 TB of data cutover with less than a minute of impact to their database. I know that's not as simple as starting on Citus and continuing to scale, so hopefully we can address this better in the future, but for now it's the best answer we have at the moment. [1]. https://www.citusdata.com/blog/2017/12/08/citus-warp-pain-free-migrations/ https://www.citusdata.com/blog/2017/12/08/citus-warp-pain-fr...
- sam0x17 8y agoYou could, for example, offer a plan that starts out extremely cheap, uses usage-based pricing, and only has Citus technology kick in when you reach the relevant scale. So < 10 GB it would just be a normal PostgreSQL node. I would use this for everything if it was like that.