|
|
|
|
|
by innagadadavida
2796 days ago
|
|
Apple internally uses Cassandra, HBase, Riak, Hadoop/Impala, Oracle, Siri Search kv store, memcache, redis, MySQL, Postgres etc etc. Each of these handle >100 TB in aggregate. Considering these applications won’t be ported to FDB, why not develop a translation later. This will also drive adoption of FDB. Having smart people work on cool things is not sufficient, you also need them to be working on solving high impact but boring problems. |
|
Writing a translation layer would be nice, "drop in" replacement can be an overkill to drive growth.
That said the three biggest factors for adoption in my opinion are developer experience, tooling and hosting.
If some FoundationDB enthusiasts made an elastic hosting service and some dedicated tooling it would be help massively to compete with others NoSQL Vendors.