I love feathers having used it for a number of projects to date. I find it's real sweet spot to be applications that have a single backend service or for creating http based microservices. However when considering it's use in a more advanced microservices design that I'd feel happy running in production, I find various roadblocks:
- Currently the plugins that provide desired capabilities (feathers-distributed, mostly-feathers, feathers-sync etc.) seem to be experimental or not well used.
- architectures similar to moleculer, hemera use a gateway service to expose services, can feathers be used in this way and can things like scaling/load balancing socket connections be done?
- in the above architectures important things like circuit breakers and fault tolerance is provided, how is this best achieved in feathers?
I realise a lot of these topics have been covered in various issues and posts however I was looking for more of a 'current state of the world' view and recommendations moving forward. I guess I'm looking to stay as much on the happy/proven path without having to bake my own functionality where possible.
I'm more than happy to contribute if some of the above capabilities are lacking currently.
I love feathers having used it for a number of projects to date. I find it's real sweet spot to be applications that have a single backend service or for creating http based microservices. However when considering it's use in a more advanced microservices design that I'd feel happy running in production, I find various roadblocks:
I realise a lot of these topics have been covered in various issues and posts however I was looking for more of a 'current state of the world' view and recommendations moving forward. I guess I'm looking to stay as much on the happy/proven path without having to bake my own functionality where possible.
I'm more than happy to contribute if some of the above capabilities are lacking currently.