2 ms·
The way I see things now: - Avoid this entire conversation if you can (web only, blazor, live wire, business constraints, etc.) - Use JSON if your API is expo
by bob1029 5y ago
The way I see things now:
- Avoid this entire conversation if you can (web only, blazor, live wire, business constraints, etc.)
- Use JSON if your API is exposed to the general public. Keep the nesting of complex types to a minimum, preferring to reference nested items by identity rather than placing them inline.
- Use out of band mechanisms if your API is very complex and/or shared between business entities only. Example of this being SOAP/XML.
We have been consuming WSDL files for purposes of integrating with a complex banking system. I would argue that JSON would make our jobs much harder in this particular case.
The primary reason I don't like the XML path is because of the up-front schema sharing session. Once you get over this and run your codegen, life is actually really easy. For example, I enjoy having my compiler yell at me when I try to send a string vs a Datetime to a vendor endpoint.
- jrochkind1 5y agoGraphQL?
- gautamdivgi 5y agogRPC if you need some sort of static typing over https and don't want vendor lock-in. SOAP/XML works too. It's been a while since I looked which open source toolkit supported it. Problem with SOAP/XML is that although its not supposed to be "Java specific" it is mostly "Java specific".