I assume not because every comment made would not be visible until cache expired. Unless they have a way to expire the cache (which is not dependable on most CDNs?)
"a stateless web app serving 100k requests on a tiny server and putting a CDN / caching layer in front of it"
That's a great question. For "live" stuff, it seems to me that Pheonix brings so much joy and simplicity, I'd happy pay for memory and hopefully scale in a sustainable way. This is all theoretical until we get a successful app, but it's good to see the future paths :)
Have been looking at the fly/Phoenix combo for a while
The one thing I can't wrap my head around is scaling, and the cost of scaling.
If this app magically exploded to 10,000 users at one time:
1. How do I scale with Fly.io? Can I autoscale, but somehow cap at a cost?
2. What parts of the stack would I have to pay attention to? Erlang/Elixir seem to handle a lot of the complication?
3. Are there (hidden?) costs that would concern me at fly.io with 10,000 simultaneous users? Or is there a clear way to estimate the costs at different points?
thank you - this looks very promising and (more importantly) fun!
The guy is problematic.