Re:Things I wished more developers knew about databases
by earhart on Wednesday April 22, 2020 @10:55AM
(#22946174)
That gets tricky if one of the writes fails.
Re:Things I wished more developers knew about databases
by hobs on Wednesday April 22, 2020 @10:59AM
(#22946246)
Generally you get two phase commit involved here, or an asynch mirror that you can restore over if there's failure.
Re:Things I wished more developers knew about databases
by smilliken on Wednesday April 22, 2020 @11:26AM
(#22946548)
Two phase commit makes a promise it can't keep. CAP theorem is not amused.
It's slow, complex, a leaky abstraction, and ahould be avoided for better consistency models.
Re:Things I wished more developers knew about databases
by hobs on Wednesday April 22, 2020 @11:31AM
(#22946610)
I generally couldn't agree more, but yet its the first tool in the toolbox for a lot of databases.
Re:Things I wished more developers knew about databases
by smitty1e on Wednesday April 22, 2020 @10:06AM
(#22945672)
That sort of flexibility does not sound as though it would scale well as the data get big.
Re:Things I wished more developers knew about databases
by madhadron on Wednesday April 22, 2020 @10:55AM
(#22946184)
Define "big." Double writing in some form is the only option for live migration and you either bolt it on later or plan for it now.
Re:Things I wished more developers knew about databases
by smitty1e on Wednesday April 22, 2020 @02:23PM
(#22948600)
When the overhead of the double writing becomes substantial enough affect the architecture.
That will afford migration with as close to transparent migration with as reduced a downtime or no downtime.