2 ms·
For JSON contracts that are of any reasonable level of complexity (many levels of nesting), I prefer to have the same serializer & strong type system on both en
by bob1029 5y ago
For JSON contracts that are of any reasonable level of complexity (many levels of nesting), I prefer to have the same serializer & strong type system on both ends. A common use case here is serializing dynamic business types as JSON in and out of blob columns.
For what its worth, I have had maybe 2 hours total worth of struggles with JSON serialization over the last as many years, and we use it for pretty much everything. The biggest pain point for us is implementation-specific. Refactors of namespaces & dependent assembly names can cause trouble with polymorphic serialization (which can absolutely be secure if used responsibly). The only other pain point experienced is with regard to nullable vs non-nullable fields - again only a problem after a change takes place relative to pre-existing JSON documents.