3 ms·
A single database instance can host multiple independent schemas. No need to pay for more. Treating a database as an API is more than doable, but the whole team
by mixedCase 5y ago
A single database instance can host multiple independent schemas. No need to pay for more.
Treating a database as an API is more than doable, but the whole team needs to be on point with the necessary shift in expectations, as well as the shift in tooling and best practices.
- gkop 5y agoI was surprised how well treating the database as an API worked at one series A company. We had a single database schema shared by ~5 services. The coordination cost wasn’t bad, and I don’t recall any major issues. It was a big net win for our velocity. I’d do it again, if I had the guts.
- xvinci 5y agoI meant the overhead - in the case of two services - of managing and developing two sets of schemas and a mechanism of data exchange (be it rest apis or queues. both come with a producing and a consuming side). There are many reasons where that makes sense (e.g. both ms have to evolve the shared storage schema in different directions) but I would not do it out of the box every time like the author implies.