- Anything outside of int32 must be encoded and decoded as a float. Oh the bugs/crashes this has caused. - It is way too easy to change the schema and wreak ha

- Anything outside of int32 must be encoded and decoded as a float. Oh the bugs/crashes this has caused. - It is way too easy to change the schema and wreak havoc with downstream users. - Some libraries will encode empty strings as null for instance, some as empty strings. Some will have empty objects, some null. Switch some configuration, change your serializer, ORM or anything that touches your data. Everything will work perfectly in your code, but json output can change and you will again break your downstream users. If you are designing an API, use protocol buffers. Json maybe as an optional output/input to your service. Keep it as a discouraged dirty optional feature and you will save yourself a whole lot of debugging and time wasting.