video-on-demand-on-aws VS firebase-admin-go

S3 is great but someone woke up one day with a $8,000 bill on AWS while encoding videos. There's also this architecture overview in the repo, if you're planning to stream media adaptively.

> Can you give some examples?

Someone woke up one day with a $8,000 bill while encoding videos:

https://github.com/awslabs/video-on-demand-on-aws/issues/48

There's also this pretty architecture overview in the repo:

https://github.com/awslabs/video-on-demand-on-aws/blob/maste...

In my opinion, it's too complex and I'd prefer a more simple solution to get to market faster.

Imagine adding just a few lines of code to get started instead of setting up all these things on AWS, where you might end up paying up to $0.12/GB for outgoing bandwidth as well.

I recently tried to fork the firebase-admin-go package and add a few edits that I need for a project. I decided to use a replace directive in my go.mod file but when I do I get this error:

I found this Github Issue on the official firebase SDK asking about event listeners. The developer asking the question wrote an entire addition to integrate event listeners into the SDK and even signed a Google Contributor Licenses but it does not look like this will be integrated. Is there a way that I can take the logic that is already written and put it into my application rather than writing a wrapper around the firebase REST streaming API? It is essentially already written with this pull request.

To use it without the JS SDK, you need to create a server which integrates with their API. This usually means pulling an SDK in on your server which is often okay, though I did find their Go SDK (https://github.com/firebase/firebase-admin-go) rough on the edges. We ultimately abandoned using the service... I think if your integration requires any fine tuning or integration with other services, you might want to look elsewhere.