Can I generally use off-the-shelf postgresql bindings in most languages with CitusDB, or are there things about CitusDB that would require custom bindings? If the latter is true, for what languages are bindings available (ruby/node.js/crystal...)?
I will throw money at you if you set up a basic/crappy $5/month (or free!) node that can gradually get upgraded in-place to higher and higher plans to the point where it is using your sharding technology etc.
I appreciate your response, but my point is this: people are going to go with the service that they can scale up from $5/month to $28,000/month without any interruptions or switching of providers. It would be great to see you guys try to tackle this problem with that in mind, and I think you could do it really well. I just think you underestimate how many people want their infrastructure to cost nothing when they are in pre-launch mode, and will let their pre-launch infrastructure dictate their post-launch.
To reiterate: I get that your service doesn't start to scale well until the $99/month price point, but I don't care about performance until I'm at that price point anyway. I'd rather have the ability to start from nothing with OK/crappy performance, then have to switch services right when my product starts getting traction. It's about continuity and scaling up from nothing.
These guys need to add a cheap/freemium tier so small-time developers can scale up their services from nothing. $99/month for their trying-it-out/developer plan is a bit overreaching.
update: Because of the popularity of this article here and on Slashdot, and the controversial views I express in it, I have been terminated from my contracting position at my current employer, which was my main source of income. You can read more information and (if you like) donate to help my cause here: https://www.gofundme.com/lost-job-bc-of-engineering-article
I could have just written: "Even if we ignore the unpredictability of humans, there are deep, logical, Halting Problem-related reasons why coming up with accurate software development time estimations is idiotic." But then this wouldn't feel like a grand project that points out something fundamental perhaps a lot of people have missed, and doesn't convey the degree to which I think the halting problem actively limits what we humans can and can't do. I didn't word it a particular way to sound intellectual, I chose each word to convey the pseudo-religious experience of realizing that those hidden gotchas you experience while you code on a daily basis are there because of something fundamental, on the order of a physical law of the cosmos, so quit trying to reason around that fact with time-based estimations that pretend that everything is always going to go even close to what was planned. If you can find a non-douchy-intellectual way of giving me a pseudo-religious experience, then by all means, show me. It should sound like morgan freedman is reading it from the script of Cosmos.
Sorry you'll have to deal, for undergrad I double majored CS and Philosophy. That's literally my favorite 2-sentence section in the entire article, and I spent about 45 minutes to an hour revising just that section for flow and meaning. I am going to cry now.