R&D Firebase as a storage engine for this real time data

[JoeEarly]

Making use of Firebases Topic Messaging service to push real time level data to users who opt in.

https://firebase.google.com/docs/cloud-messaging/android/topic-messaging

(Auth may move here and ditch the need for Passport/JWT maintenance )

[goofballLogic]

This is quite a different architecture from using S3 as a "dumb" datastore. Should be possible, but you probably wouldn't want to allow free, unfettered access to the data such as the current client allows. I imagine firebase will charge for their push service at a certain point?

The S3 solution means you don't need credentials or a token or anything to query the data because S3 is very cheap.

[goofballLogic]

added this to the "waterlevels" project

[JoeEarly]

Firebase isn't that expensive that its off putting.

Again am not 100% sure on the best approach, but it needs to be maintainable for me in the long run. And I suppose free is always better than a fee

If we keep the raw data in S3, and with this client app offering the different query functions, then my front end react calendar component can call it fine.

Mongo then stays for everything else and use JWT to protect the sessions which is easy to add I think to the current auth stuff I did

[goofballLogic]

Ok I'll tag this as an enhancement ⁣Sent from BlueMail ​

…

On 27 Jun 2019, 17:30, at 17:30, Joe Early ***@***.***> wrote: Firebase isn't that expensive that its off putting. Again am not 100% sure on the best approach, but it needs to be maintainable for me in the long run. And I suppose free is always better than a fee If we keep the raw data in S3, and with this client app offering the different query functions, then my front end react calendar component can call it fine. Mongo then stays for everything else and use JWT to protect the sessions which is easy to add I think to the current auth stuff I did -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #8 (comment)