unlawfulbooger@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 1 year agoThe rule of growthi.imgur.comexternal-linkmessage-square68fedilinkarrow-up11Karrow-down10file-text
arrow-up11Karrow-down1external-linkThe rule of growthi.imgur.comunlawfulbooger@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 1 year agomessage-square68fedilinkfile-text
minus-squareryannathans@lemmy.fmhy.netlinkfedilinkarrow-up3·1 year agoThe only advantage would come if you could rewrite lemmy to be serverless
minus-squareAnonymousDeity@beehaw.orglinkfedilinkarrow-up1·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-squaresteal_your_face@lemmy.mllinkfedilinkEnglisharrow-up2·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.