By "tabular" data I'm referring to the sort of data that might be stored in a relational database. The specific characteristics of tabular data I want a serialization apparatus to take advantage of is the usual SoA vs AoS tradeoffs. As examples, if every item has a boolean field and there are many items, it may be advantageous to store chunks of booleans together as bits. The reason I'm interested in something other than for example, an SQL database, is that I don't need support for queries, I want to store data as a file or set of files instead of in a centralized per-machine database, I want richer typing, and my tabular data is bundled with data that is less amenable to the relational model such as variable length lists.
Is Cap'n Proto appropriate for this sort of use? If not, is there an obvious alternative that is? Thoughts? Thanks. -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
