If I run Strapi on Kubernetes. Can I spin up multiple pods for the back end or will that cause conflicts?
I never had problems running multiple replicas of a Strapi application, in both AWS ECS and Kubernetes, since Strapi backend and admin are stateless applications.
My only concern the database autoupdate, when some content type is changed. All the replicas will try to update the database at same time. I’m still trying to find some way to disable this autoupdate, and trigger it manually, like some kind of migration.