Microservices underpin almost all modern web services. A single product might have dozens of APIs feeding directly into its frontend, or into other services.
Testing and updating the functionality of these APIs is fraught with challenges. Doing so usually requires spinning up entire testing or staging environments replete with all other microservices and data. This doesn’t scale and takes significantly longer for, what might be minor, API changes.
Signadot sandboxes allow you to preview your API changes with real data and using all other live microservices, all from a single code branch.
Here we want to take you through setting up a sandbox environment to make a change to an existing API and understand the downstream effects of the change.
Let’s first setup our Signadot account and the prerequisites needed. If you haven’t already, you can create a Signadot account here.
Once you have each of those installed, head to your Signadot dashboard and to ‘Clusters’ and ‘Connect Cluster.’ Choose a name (here we’re using ‘ms-cluster’). Take note of the Token value that is shown on the next page as you’ll need it for the next step (once you close this page, it won’t be shown again).