adrien-treuille
Joined 7 years ago
Joined 7 years ago
I've never used Lambda, but your question prompted two thoughts:
(1) Streamlit has an interesting property which we haven't yet publicized which is that if you:
python a_streamlit_sctipt.py
instead of
streamlit run a_streamlit_sctipt.py
It runs a_streamlit_sctipt.py from top to bottom but disables all the Streamlit code! This is intended so that Streamlit scripts can doouble-duty as both ordinary python scripts and inline visualizations. Now. I'm not sure how this would behave with lambda, but I'd be very curious to hear your experience.
(2) The more standard Streamlit approach would be to deploy your model to lambda, and then write a Streamlit app which connects to that model on lambda and visualizes your model.
I hope that helps. Please do share your experiences! Streamlit is an emerging technology and we're still very much figuring out how it fits in the ecosystem. I think figuring out Streamlit <-> Lambda is important and I very curious to hear what you find!
Btw, the best place to continue the conversation would be at discuss.streamlit.io because there are probably more people there with Lambda experience who could help you. Also, more Streamlit users could benefit from your insights. :)
Ian:
Thanks for that comment. You're exactly right: Streamlit adapts a React-like model. In fact, the connection goes deeper than the post describes. For example, to make it efficient to run the same script repeatedly, Streamlit does packet-level deduplication. If you generate a lot of data and send it to the browser, only small deltas need be sent to update the UI.
We have a list of future blog posts we hope to write and one of them is (cheekily) called "Streamlit is React for Python." ;) (Not quite true, more of an imperfect analogy!)
So it made me really happy to see someone drawing that analogy already. Thank you. :)