We already created a more scalable combination of GitLab components in the previous chapter. But, of course, there are even more options. If you wanted go for a 100% breakdown into smaller, more cloud-native components, you would have to stop using the omnibus-gitlab package. If you did that, an elastic, fault-tolerant database service such as Aurora could be used from Amazon itself and other Amazon-specific services such as ElastiCache. It would mean much more management overhead, but it could be the way to go if you have the time and money to build big production sites. It would be harder to switch to another cloud vendor, though.
Because we like to use an example that can be deployed on another cloud and because the omnibus package is used throughout this book, we will use that again.
In the following diagram, you will find the third...
