4 ms·
At Appcues, we use a combination of both approaches. We have our Elixir backend where we need some combination of: - Low latency -- Lambda + API Gateway reque
by gamache 10y ago
At Appcues, we use a combination of both approaches.
We have our Elixir backend where we need some combination of:
- Low latency -- Lambda + API Gateway requests typically incur a ~200ms invocation latency
- Persistent connections, e.g. WebSockets
- High performance
- Continuous usage, let's say at least ten calls per second all day every day forever
For everything else, Lambda and API Gateway have been fantastic, even without a framework like Serverless. It's so cheap! It's so convenient! It's so reliable-enough!
But we couldn't get along on a 100% Lambda backend, far from it.
- dfischer 10y agoI agree with this a lot. Especially on the web socket front. I've been thinking of an ideal structure for this. I haven't decided between elixir or bet in with Google and Firebase.
- gamache 10y agoFor what it's worth: we use Firebase in our stack too, but at this point it's confined to our customer-facing dashboard (as opposed to our end-user-facing service). I don't like it when my critical systems depend on services out of my control, especially when those services go down for hours or days at a time -- as Firebase DB has done twice in the last year, for us.