Sharing the database isn't a huge deal as long as the data doesnt cross boundaries. Place them in distinct schemas and you essentially have isolation.
Sharing the database isn't a huge deal as long as the data doesnt cross boundaries. Place them in distinct schemas and you essentially have isolation.
This is too close to a scene in the book. Frank meant well.
It can work, but it can be weird and strange as well. Certainly using one db cna work, though if the db is down, all services are down, which is partially against the idea of database. Also reading from multiple schemas to join data seems like a waste
i feel like if the underlying stuff isn't totally separate and independent you're not getting the idea. we had a situation where no one could update their service before midnight because they were too tightly coupled. the opposite of what we wanted. they were all using a single workflow db!