@[email protected] to [email protected] • 2 years agoThe rule of growthi.imgur.comimagemessage-square66fedilinkarrow-up1999
arrow-up1999imageThe rule of growthi.imgur.com@[email protected] to [email protected] • 2 years agomessage-square66fedilink
minus-square@[email protected]linkfedilink4•2 years agoThe only advantage would come if you could rewrite lemmy to be serverless
minus-square@[email protected]linkfedilink1•edit-22 years agoI mean I’m sure Lemmy’s server process is stateless, I’m sure it could use CloudRun/ECS pretty efficiently and that wouldn’t really require a rewrite (unless the process is stateful for some reason)
minus-square@[email protected]linkfedilinkEnglish2•2 years agoIt’s possible to run Lemmy on kubernetes so I assume you could on ecs as well. I’m pretty sure the Postgres db manages state and not the process.
The only advantage would come if you could rewrite lemmy to be serverless
I mean I’m sure Lemmy’s server process is stateless, I’m sure it could use CloudRun/ECS pretty efficiently and that wouldn’t really require a rewrite (unless the process is stateful for some reason)
It’s possible to run Lemmy on kubernetes so I assume you could on ecs as well. I’m pretty sure the Postgres db manages state and not the process.