2 ms·
As a counter example, Django was "ready for production" for ages before a third-party migration app (South) came along, let alone built-in support
by airstrike 6y ago
As a counter example, Django was "ready for production" for ages before a third-party migration app (South) came along, let alone built-in support
- steve_adams_86 6y agoRight. Best practices are all well and good, but the reality is that tons of people are running in production with no migration strategy. I'm not saying it's not important or that Prism is fine without it. I wouldn't choose software without a tried, tested migration strategy available. Just... To a lot of people I've worked with, migrations are a nice-to-have that will probably never happen.
- danpalmer 6y agoIt was but at the time the state-of-the-art for migrations was to hire a DBA and have them do it. That's much less common now with migrations and database operations being owned by development teams much more, so the need for migration tooling is much higher now, especially in what I expect Prisma's target market is.