We're looking to merge several independent web applications into a single production environment. Here's our current setup:
- We have various applications built on mixed tech stacks.
- Our plan involves using a single hosting provider, with Hostinger as a main contender.
- We're aiming to redesign our database structure into one centralized MySQL database, which we're calling the 'mother DB.'
- Our goal is public deployment, but we need to ensure scalability, stability, and maintainability.
Some factors we're considering are:
- No existing VPS or cloud architecture in place.
- The systems were built to operate independently.
I have some concerns:
1. Is it feasible to use shared hosting for multiple production systems?
2. Would it be better to isolate each application at the infrastructure level by using VPS or containers?
3. Should we stick to a single shared database or create separate databases for each application on the same server?
4. What major risks should we watch out for, such as performance bottlenecks, schema coupling, or failure cascades?
We're open to suggestions based on anyone's experience with deploying multiple applications in a single environment, especially in relation to shared hosting versus VPS options. Thanks in advance!
3 Answers
To clarify on the database management, when we say 'mother DB,' we refer to a MySQL server housing different schemas for each app, not a shared schema with mixed tables. Each app would get its own schema and user with limited access rights. From your description, it seems like a decent strategy using a VPS with a reverse proxy. Maybe consider moving heavy analytics to a reporting setup to avoid stressing your OLTP tables. Always ensure everything is distinctly managed to prevent issues like race conditions. Your plan sounds like a step in the right direction! Just keep an eye on governance for the core shared schema.
I don't think shared hosting is a wise choice for multiple production apps, including with Hostinger. The resources are shared, meaning if one app has issues, it can affect all of them. Opting for a VPS or containerized setup keeps each app isolated, leading to better stability and easier scalability. When it comes to databases, a single 'mother DB' isn't recommended either. Instead, separate databases for each app on the same server is a much cleaner and safer practice. Overall, a VPS with isolated apps and individual databases will set you up for success.
It depends on several factors, like whether these apps are actively maintained or built in similar environments. My approach would be to merge less critical or lighter apps into one environment while keeping the important ones separate. The database situation is key too. If you mean having one server with separate virtual databases, that's generally okay, but it depends on how demanding your apps are. Mixing tables in a single DB is riskier unless the apps are structured to handle that.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads