UtopiaSync Custom Configuration

What does this mean for you?

UtopiaSync is uniquely configurable. You can mix up databases, kubernetes clusters and link them all together to work harmoniously. The easiest way to highlight the configurability of UtopiaSync is to share some configuration examples.

UtopiaSync has an environment section which allows you to configure various things.

Example 1: Customer Database Cluster

Lets say you have a version of UtopiaSync up and running happily. You get a project which requires the documents to be encrypted. Your existing projects do not carry sensitive data and encryption at rest is not required, so what is the best way to manage this? UtopiaSync allows you to create a second completely independent database cluster that contains your encrypted databases. You can save this configuration in the Environments section, lets call this EncryptDB. You can now link any Organisation to EncryptDB, this means that when any processes inside your organisation linked, UtopiaSync will run the job using the encrypted database. Example 2: Customer Workers cluster

In this example you have a project which requires access to an environment which is running a special tunnel which is not easily accessible. It is also only needed for a single process and the thought of having to move your whole setup into this new environment to enable access to this tunnel does not seem elegant. No problem, Utopia can help you here. All you need to do is fire up a new Kubernetes cluster within this new environment, fire up a new microservices pod there (let's call this tunnel-micro) and as long as it has access to the queuing database it will sync right up.

What you can do now is go into your Environment section and create an environment called tunnel-micro, lets call this environment ENV-TUN. How you can navigate to the connector you need to run there and link it to this environment ID and when those jobs are set to run, UtopiaSync will make sure they run in your new cluster and not the existing one.

These two examples explain how you can create different environments to link within your UtopiaSync setup. But it doesn't stop there, you can mix and match clusters and databases however you like, you can also link environments to a more makro level like an organisation or more micro down to connector level.

whether you want multiple clusters or single clusters with multiple databases, through to multiple kubernetes clusters all linked together some running on communcal databases, other on independant ones, some running stateful sets others running standalone setups. Anything is possible with UtopiaSync. If you have any questions around this please get in contact with us!