"the company is not quite sure what will happen when the database goes over 100TB in size" - dammit, I'm not risking my porn stash with that thing then.
NoSQL database startup FoundationDB has made its ACID-compliant tech generally available, after an extended beta that has seen over 2,000 people try out the company's unorthodox database. The FoundationDB database is a key-value store that also allows for different data models – such as JSON documents, graphs, and SQL (via …
transaction limit of 10,000,000 bytes, key size limit of 10,000 bytes, and value limit of 100,000 bytes
Nice to see that BCD is still alive :) (and no, that's not "Boyce-Codd Database")
WTF is a "server process"?
https://foundationdb.com/pricing and click on "Process"
Turns out this is basically per-core licensing: $1188 to $2388 per year per core. So this is going to skew the type of hardware you buy: i.e. better to buy quad core 3.0GHz instead of hex core 2.0GHz processors. Hyperthreading counts as cores too.
But who's going to bet their business on this, when they have you over a barrel? This is a completely closed-source product, so no chance of anyone forking it. At least if you use Oracle or MSSQL there is always the potential to migrate to another database, painful though it may be to deal with all the SQL incompatibilities.
Re: WTF is a "server process"?
A "server process" is an instance of the fdbserver process running on a machine. Each machine running A FoundationDB server obviously needs to have at least one fdbserver process running. However, ONLY one is necessary to take full advantage of all of the disk I/O, memory, and network capacity of the machine. It is normally one of these factors that is bottlenecking a server, and many times adding additional processes to a multi-core machine will add a negligible amount of performance. However, there are some workloads that may be bottlenecked on processor power, in which case you CAN (but don't have to) run additional processes.
So, to be clear, you could run a 24 machine cluster of dual or quad core servers with just 24 processes and likely get most of the performance out of them that you would if you were filling all cores with processes.
BTW I am one of the founders, not just some random guy on the internet :)
limits deployment to clusters of up to 6 processes per month
A FoundationDB process is a single worker process you run on a computer
OK, I think I grasp what a process is. But what's a "process per month"? It sounds like floating-point ops per foot. or GHz per millibar.
Or does this in fact mean that every month you can deploy to 6 cores? So at the end of the year you have 72?
It just means that each month, you can run 6 processes for free in production. You don't have to do any crazy math. If you in any month need to run more than 6 processes in production, you should get in touch us and set up commercial licensing and support. If in subsequent months you drop back to or below 6 processes and you don't want support, you can cancel your support / commercial licensing and go back to 100% free.