Email or username:

Password:

Forgot your password?
Top-level
wikiyu

@dansup @pixelfed

Years ago when i was younger i would suggest "procedure" approach -> move all DB stuff to as encapsulated procedures as possible (crud)

then making a migration BUT with stay on application side to procedures that are changed with migration.

Now? I dont know, i didnt thought about stuff like that for at least 4? 5? years as i am doing a bit different part of it development now then then.

2 comments
dansup

@wikiyu @pixelfed Well, we do use Laravel, so we can make versioned migrations but this is a bit more complex than a simple migration.

Data needs to be slowly synced to prevent downtime

wikiyu

@dansup @pixelfed

Do you really need "no downtime"?

I think that stuff like that doesnt have to be done seamless...

More important is stability and being sure of doing it right, then "no downtime"

Go Up