Hi Chris....Can you provide some insight from your experience how you would go about transitioning and scaling large database procedures that hit many tables and take a very long time process ? Have you ever had to deal with situations like that in re-engineering legacy? My current view is the long brute force approach for long term gains. Extracting apart the procedure and looking at in memory options like redis or possible table pinning.
FWIW, the book does have a section, 6.1 What to do with the DB. Chapter 6 is about The Big Rewrite though so, since I don't subscribe to the idea of doing big rewrites, I haven't read this chapter in detail.
First, you drop a couch from the plane, THEN you surf it. Here, take this tiny ad with you:
a bit of art, as a gift, that will fit in a stocking
