UPDATE working on this here!
so… I've had this weird idea recently...
In git (and in other secure + distributed systems) you have a tree of hashes where each object is identified by it's hash and objects contain pointers to other objects. They just have the hash of other objects stored inside them.
| DEP | ANNEE | RESOLUTION | |
|---|---|---|---|
| 01 | 2012 | 20CM | |
| 02 | 2013 | 20CM | |
| 03 | 2013 | 20CM | |
| 04 | 2012 | 20CM | |
| 05 | 2013 | 50CM | |
| 06 | 2012 | 20CM | |
| 07 | 2014 | 50CM | |
| 08 | 2013 | 50CM | |
| 09 | 2013 | 50CM |
How do you send information between clients and servers? What format should that information be in? What happens when the server changes the format, but the client has not been updated yet? What happens when the server changes the format, but the database cannot be updated?
These are difficult questions. It is not just about picking a format, but rather picking a format that can evolve as your application evolves.
By now there are many approaches to communicating between client and server. These approaches tend to be known within specific companies and language communities, but the techniques do not cross borders. I will outline JSON, ProtoBuf, and GraphQL here so we can learn from them all.
