Are there any generally accepted standards for inter-microservice communication? Or does everyone just go it their own?

• wasi-messaging

  1 15 4.1

  messaging proposal for WASI

  

Yes. However, consensus can be achieved in some cases. This PR wasi-messaging Refactor ft. stakeholder review #9 covers some ground re messaging, or if you prefer, "microservice communication".

• telnet-client

  4 150 5.9 TypeScript
  

There are many ways to achieve the requirement. Server-Side Events (text/event-stream implemented via EventSource); WebSockets; WebRTC data channels on Web, libdatachannel on Web and outside of Web; Fetch Standard with duplex: 'half' provides persistent bi-directional communication; QUIC (WebTransport); WebTorrent; DirectSockets now exposes TCP/UDP sockets in certain contexts, see GoogleChromeLabs/telnet-client, depends on TypeScript, Webpack, Node.js, npm.

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• The gist

  26 5,473 9.6 TypeScript

  BullMQ - Message Queue and Batch processing for NodeJS and Python based on Redis

  

I use bullmq with node

Suggest a related project