Our services currently allow us to specify multiple types, but only to enable one at a time. For example, we have to choose between Apache and Nginx for an http (web) service. In this case, it (almost) makes sense, since they'd both be vying for the same standard ports (80, 443). However, other services wouldn't likely have such collisions. For example, PostgreSQL listens (by default) on 5432, and so could presumably live beside MySQL (listening on 3306) on the server just fine.

We're currently working on a 'storage' service that would either move the files directory out of the sites' dirs, or move the sites' dirs completely out of platforms. The current service implementation forces this to be an either/or choice, or to implement entirely different services.

#881962: Use Cases: One server with multiple service instances on different ports is related, but goes further, suggesting having multiple instances of the same service type. @Vertice appears to suggest having multiple server nodes/contexts (to allow for migration).