3 ms·

Choose what makes sense for the long-term and uses (storage, querying, extensibility, whatnot). I see little reason to use a schemaless thing like JSON anymore.

Choose what makes sense for the long-term and uses (storage, querying, extensibility, whatnot). I see little reason to use a schemaless thing like JSON anymore. If I was putting together a new project I'd go with capn proto. If I was putting together a new project and wanted a universal RPC stack, I'd go with Thrift (eventually capn proto when it gets more languages w/ RPC support). That's just my opinion though, others will vary. The important thing to remember about your choice is that it's going to be really difficult if not impossible to change later on down the line, so choose wisely.

maximveksler 12y ago
That’s a good and very viable option to consideration, and is a factor for when you start focusing on the direction but I think it’s unwise to being with narrowing down the options based on such constrains as IMHO this does not lead to the optimal solution but instead to a compromise. // (btw, totally OT) If you’d like to know where I’ve learned about this reasoning, kindly introduce self to http://hpmor.com http://hpmor.com (chapter 35-45, can’t remember more specific than that).