shapeshift
Spin up services hostings and databases
This one might be targeting @kevin but we need to setup all the databases for the services:
- user
- notification
- swap
And database related, we need to determine:
- Do we want a single database
- Do we want one database by service
The way I designed the microservice mono repo is one db by service, if we want to change that it will require some architecture change
One question remaining, we might want to create a separate ticket for that:
- How are we delivering those service? It should be on merge on main from the CI but for now as I don't know where it will be hosted, it's quite hard to implement
AC:
- Hosting for the micro services is up and usable
- DB for the micro services are up and usable
- Secrets are added to the github repository of the mono repo (https://github.com/shapeshift/microservices)
@kevin had a thought use pulumi controlling state revisions fallback etc. as a package. then give exposure accross KUBE, AWS, and such.
we also have to think about migrations. joy.
During the meantime, deployed a railway instance so we can test on dev envs and iterate on what we want to do with notifications, improve the wording etc