Thanks for your insight. It's incredibly interesting! I suppose with so much inter-departmental exchanges of information running on legacy HW/SW, I can see why it might need several hours of downtime.
You’re welcome. I definitely get your question, no one would intentionally make a transactional system like that today. With all the advances we have made it just isn’t necessary anymore.
Although there are a few places where I can think that this pattern kinda still exists today for good reason. For example, compliance reporting systems where data is sliced off on a batch basis on some interval and pushed into a different DB for read-only reporting etc. We did that for public accounting compliance reports so the data was locked and non-updatable that produced the reports. But there are other patterns which can be used too.
Comments
Thanks for your insight. It's incredibly interesting! I suppose with so much inter-departmental exchanges of information running on legacy HW/SW, I can see why it might need several hours of downtime.
You’re welcome. I definitely get your question, no one would intentionally make a transactional system like that today. With all the advances we have made it just isn’t necessary anymore.
Although there are a few places where I can think that this pattern kinda still exists today for good reason. For example, compliance reporting systems where data is sliced off on a batch basis on some interval and pushed into a different DB for read-only reporting etc. We did that for public accounting compliance reports so the data was locked and non-updatable that produced the reports. But there are other patterns which can be used too.