Updated Why FlatBuffers vs other options? (markdown)
parent
9b7e851543
commit
a2b0bcdf13
|
@ -11,4 +11,4 @@ This is a long topic, but one thing to highlight is the _range_ of possible use
|
||||||
-----json------ |
|
-----json------ |
|
||||||
```
|
```
|
||||||
|
|
||||||
Meaning even if you don't need to be particularly fast or flexible with your current use-case, FlatBuffers scales in every direction, with more representation choices than any other serialization system, and more API choices (use with JSON, use with object API etc)
|
Meaning even if you don't need to be particularly fast or flexible with your current use-case, FlatBuffers scales in every direction, with more representation choices than any other serialization system, and more API choices (use with JSON, use with object API etc), and easy ways for the first 3 options to work together (struct/table/flex).
|
Loading…
Reference in New Issue