Deployment Pros Cons - miscellaneous
One Kubernetes Cluster to Store all sites
Pros
Score
Pro
-
1Central location for everything
-
2Probably easier to add sites with SSL support instantly ( maybe not )
-
3Only have to manage one database
-
2Add large scale Kubernetes management to resume
-
2Scale up sites from one central location as needed
-
1Could be easier to implement security features at the NGINX Ingress because it would only be in one location
-
1All pricing and nodes are in one cluster
Cons
Score
Con
-
1Central location for everything
-
4If the cluster gets attacked then all sites could be under attack
-
1Potential difficulty with setting up automation of SSL certificate creation
-
2Very real potential of difficulty with handling pods and networking
-
2Have already seen issues with trying to communicate between pods, although that could probably be fixed
Multiple individual servers
Pros
Score
Pro
- 1-5 Max configurability for each server
- 1 Individual mongo instances that are only accessible from that server
- 3 Increased security because isolation from other sites
- 1 Build skills with managing multiple servers
- 5 Feel more comfortable knowing that each site is completely independent of the others and is therefore resistant to total failure
- 1 Sites built under this will follow a consistent template and will be therefore easy to switch between and manage.
Cons
Score
Con
- 2 More time consuming up front
- 2 More maintenence time likely
- 2 Might be more expensive for lower quality. Won't be able to split a strong dedicated compute server among my sites.