That is one approach you could take, but thats not entirely necessary with our container platform. Each WordPress container is standalone and can handle its own database, and we can scale each container individually based on its needs.

So if you have 1 container hosting your database, and then multiple WordPress containers to access that database you’re going to need additional resources to host that database container so it doesn’t take all your installs down, and if something goes wrong with that container you will then disrupt all your other sites. Which is a mulitentant style approach, and suffers from the same flaws as any mulitentant system.

Or as I said, you can simply let each install have its own database, and then give each container the resources it needs depending on traffic. So some of the containers might not use or need much where as others might need more memory.