>Considering these applications won’t be ported to FDB, why not develop a translation later. This will also drive adoption of FDB. Writing a translation layer

>Considering these applications won’t be ported to FDB, why not develop a translation later. This will also drive adoption of FDB. 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.