It seems weird in 2025/2026 we are still discussing the baseline of getting a storage working.
Feels we’re spending too much time discussing the trees and not enough time getting the forest going:
* we need reliable local storage
* integrated backup
* apps installation / management
* remote access and account management
* app isolation, reliable updates
As @leef mentioned, you should transition between Lambda and <another offering> based on the current load.
I've published LambdaFlex as an Infrastructure as Code (IaC) template. It automatically scales and manages traffic between AWS Lambda and AWS Fargate [1].
This setup leverages the strengths of both services: rapid scaling, scaling down to zero, and cost-effectiveness.
After reading the parent comment - I thought to myself “so what”.
But after reading it on the product page - I fully agree: seeing clearly the targeted personas and out of scope usage significantly elevates my trust in the product and the team behind it.
I find langchain complicates more than it helps: abstractions are leaky, API is not consistent across components, and it creates overly complex components.
It's too many layers of over-engineered complexity, and it's for underlying components that are changing very rapidly, so you are getting bogged down with out-dated architecture very quickly.
I had an issue thinking UI was slow, but it turned up that mouse pointer integration issue - simple check: get a USB mouse and inject that USB device into VM.
Still not as good (as I remember VMware would provide), but better!
BTW, tested 7.0 just now -- anecdotally Ubuntu's UI does not feel any faster and somehow still depends on the resolution not the size of the window being moved