New user of the forums — but I have been developing applications using Meteor for 5 years now. Still have a large scale app in production running smoothly.
First off — I want to say that it is great how much progress the community has made, and appears to be making in the near future thanks to Tiny.
One of the things that pulled me away from Meteor and to AWS’ Amplify framework was the devops relief their framework was able to provide. I just recently found out that Galaxy now has auto-scaling — something that in my opinion came way too late — but nonetheless a key selling point that brought me back to Meteor to work on my next large scale commercial application.
I strongly believe that the next iteration of Meteor needs to incorporate or decouple the client from the server to provide flexibility for serverless / micro service operations. I understand that the state management side of Meteor makes this complex — especially with cold-starts added to the mix. But something that is new on the scene of Serverless is Cloudflare’s latest Workers feature of 0 nanosecond starts of applications.
Would it be possible to utilize this new feature in addition to their existing global low latency key value store, for state management on the server side, to run Meteor in a Serverless environment?
Sorry if this is a dumb question in advanced — I admit that I do not understand the dynamics of Meteor’s state management on the server side.