We're working on consolidating several independent web applications into a single production environment and need some guidance. Currently, we have multiple applications with mixed technology stacks. Our plan is to use a single hosting provider—right now, we're considering Hostinger—and to restructure into one centralized MySQL database, which we're calling the "mother DB." Our goals are to achieve public deployment with scalability, stability, and maintainability in mind.
However, there are a few constraints: we don't currently have a VPS or cloud architecture set up, and each system was originally designed to operate independently.
I have a few specific concerns:
1. Is it feasible to use a shared hosting environment for multiple production applications?
2. Would it be better to isolate each app at the infrastructure level using VPS or containers?
3. Is using a single shared database a good practice, or should we consider separate databases for each system on one server?
4. What major risks should we be aware of, such as performance bottlenecks, schema coupling, or failure cascades?
We're evaluating shared hosting versus VPS options with Hostinger but are unsure about the long-term scalability implications. Any architectural advice from those experienced in deploying multiple apps in a production setup would be greatly appreciated!
2 Answers
It really depends on several factors. If the apps are being actively maintained and share similar languages/environments, you might consider grouping less critical apps together. Regarding your database, if you mean a single DB server managing different virtual databases, that should work fine as long as it meets your performance needs. However, mixing tables in one database is more risky unless the apps were designed for that. In my experience, less complex and well-maintained apps can often be shared, while older apps that need specific setups should be kept separate.
Using shared hosting, even with Hostinger, isn't advisable for running multiple production apps. When you share resources, if one app lags or crashes, it can affect everything. Instead, go for a VPS or use containers, which isolate each app—this enhances stability and makes scaling a breeze. As for your database concerns, steer clear of one massive "mother DB." It's much safer and easier to maintain if each app has its own database on the same server.
To clarify, by "mother DB" we mean using one MySQL server hosting separate schemas for each system, not a single mixed schema with shared tables. Each app will have its own schema and DB user with limited permissions. We're actively maintaining the apps but they have a mixed stack ratio of 5:1, hence the plans for a VPS with reverse proxy. For analytics, we're aiming to keep heavy queries off the main tables by using reporting tables instead. I'd love any advice or best practices you might have, especially for managing migrations and schema governance!