3 ms·

Thanks! But seriously, there aren't any servers. There is a local development server included, to help you code your web site locally. But, it's not a server

• curun1r 11y ago
  It's awesome to see this because I've been planning on doing something very similar for a future project. The only major difference between what I was envisioning is that I was still going to have a few EC2 servers to maintain WebSocket connections to the client as I want near-instant responsiveness. Another minor difference is that I was planning on using a static site hosting provider like Netlify to host static content since it's a) cheaper and b) automatically uses a CDN. But my worry has been on the performance side of Lambda...that near-instant feel is going to be compromised if there's much latency introduced and I still haven't done any performance testing to see how much latency Lambda introduces. Have you done any exploration along these lines? In particular, I'll need to figure out what the consistent overhead is and how often Lambda doesn't reuse previous instances and forces db reconnects and the like.