4 ms·

Serverless could have been the future. But it’s too expensive and not worth it.

• cyberpunk 5y ago
  Our backend is 100% lambdas and it's significantly cheaper than running our services on eks. Can you elaborate on where the cost is? Definitely not cloud spend.. Engineering time? Serverless Stack takes almost all the pain away (vs serverless framework)
  • tehbeard 5y ago
    I can make a function that returns the current time in cowsay ascii art, and claim a "100% lambda serverless webscale backend". A bit more detail on the scale / general usecase or features would be handy to know.
    • cyberpunk 5y ago
      30 services (so far), maybe 400 lambdas, very little traffic, all gql apis. Pg backends, db per service that requires it, maybe 20 aws accounts (per squad). 50 devs (mix of perm and contract maybe 80/20), established multi million revenue business, not funded externally.
  • bsder 5y ago
    > Our backend is 100% lambdas and it's significantly cheaper than running our services on eks. Could you elaborate? We've got both, but we're not seeing a lot of differential in price. It could simply be we don't have enough traffic that would drive this correctly.