2 ms·
Our latest projects are built with RPC-style APIs and a BFF approach. We generate the TS client with Swagger and you effectively get strongly typed remote metho
by vyrotek 4y ago
Our latest projects are built with RPC-style APIs and a BFF approach. We generate the TS client with Swagger and you effectively get strongly typed remote method calls.
So basically, we're at SOAP again. A few more years and maybe we'll come back to Remoting?
- guggle 4y agoUsing JSON-RPC 1.0 here, with ad hoc client and documentation generation. So yes, basically SOAP-like, without the XML and "entreprise java" days cruft. Communication between frontend team and backend team is easy, everyone knows what a function is. No fiddling with ReST concepts for which everybody has its own personal interpretation. It's simple, it works.
- vyrotek 4y agoI've always been intrigued by JSON-RPC. How would you compare its benefits to something like Swagger? How do you like the extra verbosity of the message over the wire? Do you have a favorite generated TS client library?
- guggle 4y agoIt's really not about the tooling. I think you should go check this page: https://www.jsonrpc.org/specification_v1 https://www.jsonrpc.org/specification_v1 About verbosity, I'm not sure what you mean because it's has lightweight as any other JSON exchange. Of course there are other protocols based on binary messages, should you need that. But it's different.