The rule of growthi.imgur.comimage unlawfulbooger ( @unlawfulbooger@lemmy.blahaj.zone ) 196@lemmy.blahaj.zone • 1 year ago message-square42fedilinkarrow-up1589
arrow-up1589imageThe rule of growthi.imgur.com unlawfulbooger ( @unlawfulbooger@lemmy.blahaj.zone ) 196@lemmy.blahaj.zone • 1 year ago message-square42fedilink
minus-square ryannathans ( @ryannathans@lemmy.fmhy.net ) linkfedilink3•1 year agoThe only advantage would come if you could rewrite lemmy to be serverless
minus-square AnonymousDeity ( @AnonymousDeity@beehaw.org ) linkfedilink1•edit-21 year 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 steal_your_face ( @steal_your_face@lemmy.ml ) linkfedilinkEnglish2•1 year 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.