Earlier quoted context omitted.
Grpc?
The g is (allegedly) not for Google.
What's it for?
Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
11–20 of 240 posts
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#12Ions text format is a nice JSON alternative while it's binary format is very compact and allows for efficient sparse parsing. Fields are prefixed with their length so you can skip over unneeded fields or structs while only creating objects for values you'll use.
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#13Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#14Pretty neat, but isn't it like *two* formats: one binary and one textual?
One data model, two serializations of it.
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#15It seems like an odd choice to make the type "metadata" a prefix to the value, rather than a separate field. It feels like overloading. What's the advantage?
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#16I scanned the docs, and can't see what happens if you alter your data schema. Anyone know?
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#17`years::4`? I don't know. What not `4::years`? Also, symbols converted to integers means the receiving end has to already know exactly what they are.
There is provision for encoding a local symbol table: https://amzn.github.io/ion-docs/docs/symbols.html#processing...
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#18This is json with relaxed jackson parsing: quote-optional keys, comments, all doable with jackson OOTB for years now.
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#19I scanned the docs, and can't see what happens if you alter your data schema. Anyone know?
Seems like you have to handle that yourself. The serialized data includes the type, so your app code might have to have logic a la “if type1: … else: …” after parsing it.
Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format
#20I feel like a lot of file formats came out of companies, but even protocol buffers isn't calling itself google protocol buffers. What is it with modern companies putting their name everywhere they can?
Natural file extension will be .ai despite having no relation to AI