Starting working on a FearthersJS-based micro-service architecture I wonder if this module could not be a little bit extended to cover this use case. Indeed it actually already covers two main features IMHO:
- connect (or plan to connect) FeathersJS with different "message bus" technologies (AMQP, Kafka, etc.)
- perform real-time dispatch of any service event on the bus
It would be pity to develop again this in another module dedicated to micro-services.
So my proposal is to extend this module:
- add a small service proxy class that simply proxy requests/responses to a remote service using feathers-client (or the message bus ?)
- add an event in the Feathers app when a new service is created so this event would be propagated on the bus
- each node receiving this event will create a service proxy to the remote service so that any incoming request for the remote service will be dispatched to it
Let me know what you think and If you prefer to keep this module focused. In this case I would do something on my own. Thanks.
Starting working on a FearthersJS-based micro-service architecture I wonder if this module could not be a little bit extended to cover this use case. Indeed it actually already covers two main features IMHO:
It would be pity to develop again this in another module dedicated to micro-services.
So my proposal is to extend this module:
Let me know what you think and If you prefer to keep this module focused. In this case I would do something on my own. Thanks.