News for hackers. Stuff that matters.
Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by berns on Friday October 31, 2014 @01:07PM (#8539820)
Pricing pages without prices. I hate them.
Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by adwf on Friday October 31, 2014 @05:09PM (#8541149)
Usually means they are trying to sell to enterprise rather than small business. It's pretty much just a variant of "If you have to ask, you can't afford it". Pricing pages like this aren't about finding the price, but initiating a potentially months or years long sales process.

On that other hand, I guess they could just still be working out their pricing ;)

Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by snarfy on Friday October 31, 2014 @01:43PM (#8540036)
"How much?"

"How much you got?"

Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by jkmcf on Friday October 31, 2014 @02:34PM (#8540315)
You pay a little, you get a little scaling.

You pay a lot, you get a lotta scaling.

Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by kofejnik on Friday October 31, 2014 @02:48PM (#8540413)
"How about three-fiddy?"
Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by umur on Friday October 31, 2014 @10:16PM (#8541986)
three-fiddy it is! (Umur from Citus here)

I hear you, and we are working on fixing that even as it might take some time. The challenge for us is that for an enterprise, alternatives could cost literally in the millions (see Oracle pricing at $100k's for just a single 8-core commodity machine). For start-ups, we have offered Citus for prices lower than $5k per node in the past, and we provide an entirely free community version as well.

Essentially, our take is to not have pricing be what stops you from using CitusDB. And if you are an enterprise, the value you get from using Citus should far exceed that you'd get from any other alternative out there.

Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by kofejnik on Saturday November 01, 2014 @05:49AM (#8542611)
Yes, it would suck to not capture the value you create, and I think you totally deserve to be paid very handsomely for this tech, of course. Oh, and please make sure to charge extra from the energy, finance and healthcare sectors.

It's just that "please call for pricing" means a negotiation with a sales guy, which many people find uncomfortable, unless they work in corporate purchasing.

Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by sitkack on Saturday November 01, 2014 @12:39AM (#8542208)
Pricing is hard, especially on truly high tech product. It is always sold for less than it is truly worth, a hit you take for the art.
Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by justincormack on Saturday November 01, 2014 @08:38AM (#8542842)
No thats not really true, everything is sold for less than it is "truly" worth. Price discrimination works both ways, no reason to assume the seller will capture it all.
Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by sitkack on Saturday November 01, 2014 @01:13PM (#8543776)
Most of the time when garage based uber hackers make a product they lose proportionally more. Not that this is bad, but higher tech doesn't mean correspondingly more profit.
Re:Making PostgreSQL Scale Hadoop-style: Benchmark Numbers by vidarh on Friday October 31, 2014 @01:48PM (#8540079)
Products with pricing pages without prices doesn't exist in my world. I aim to forget products like that ASAP.