stale[bot]
commented
6 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Apologies if the issue could not be resolved. FeathersJS ecosystem modules are community maintained so there may be a chance that there isn't anybody available to address the issue at the moment. For other ways to get help see here.
It's good that you can write custom adapters to use anything as the backend for feathers-sync, but I'm wondering if there's anything that's "Pay Per Message" instead of a flat rate for dedicated resources.
Flat rate examples:
These have flat-rate prices, so they are always something like $5/month or $20/month. The price remains the same if you idle them the whole month, use their exact allocated capacity, or need more than their capacity (and your application may have performance issues, data-loss, or failure as a result).
Pay Per Message
Pay Per Message's advantages are not for everyone. If you know your price per message and your expected expenditure is less than the cost of a dedicated flat rate resource, then you would want to use Pay Per Message. If the cost were the same as or more, but you also anticipated insane usage spikes that would require upscaling your flat rate resource (which might not exist as a feature without downtime or on-demand) or you just wanted it to work without messing with that (or without messing with the entire server), Pay Per Message might be for you.
Unrelated to Pay Per Message, there is also "Received message once and only once" and "faster vs never drop unexpired messages" to consider.
Does anyone know of any Pay Per Message services that would be a valid backend for feathers-sync? I haven't decided my host yet for the project I'm currently working on, but I'd like to maintain a list of options.