rash on Nostr: 1. Serverless + monolith > microservices: We have just a tiny amount of expert users, ...
1. Serverless + monolith > microservices:
We have just a tiny amount of expert users, so the backend for our webapp can just run on one box and still power websockets and all my fancy blinky UI. All HA and stuff, thanks to our great devops people.
The work that needs scaling is all done serverless (by plugging together a bunch of AWS stuff). The code for that lives in a separate repo and has a different deployment lifecycle.
How do they talk to each other?
Well:
We have just a tiny amount of expert users, so the backend for our webapp can just run on one box and still power websockets and all my fancy blinky UI. All HA and stuff, thanks to our great devops people.
The work that needs scaling is all done serverless (by plugging together a bunch of AWS stuff). The code for that lives in a separate repo and has a different deployment lifecycle.
How do they talk to each other?
Well: