Can we stop using YAML for configuration and instead use a real programming language with possibly a type interface and a compiler? So much time wasted looking up possible configurations and worse, learning that some configuration will conflict with another.
Here is a real-world example built using this project. It's a full Chat Application:<p><a href="https://github.com/serverless-components/RealtimeApp/tree/master/example" rel="nofollow">https://github.com/serverless-components/RealtimeApp/tree/ma...</a><p>You can deploy this example. It contains a Create React App front-end and it uses DynamoDB on the back-end to keep track of who is connected to the Chat Application.
Amazing. I am so happy to see serverless getting more capabilities and still remaining so clean and simple. Any plans to do anything around mobile push notifications?
Two points on homepage design:<p>- Why does it take ~4 seconds to load (blank) the page? Is it a PWA with no pre-loading / static initializers?<p>- The scroll-jacking in the 1-2-3 section is broken on Safari
Having seen a lot of these types of services there is always a question about scale. In other words, these are great for quick prototyping, but at a certain level you have to move off a service like this onto a more robust infrastructure.<p>That being said, how hard is it to move the data off this platform and migrate it to another once you've reached scale?
Huh, interesting. Looks pretty similar to some of Fanout's stuff. <a href="https://github.com/fanout/flychat" rel="nofollow">https://github.com/fanout/flychat</a>
Does this method run into the typical lambda cold start problem? If not, how does it get mitigated without say, a regular cron job polling the endpoint?