3 ms·
this sounds backwards. i’ve worked at multiple places with the one big legacy mysql db. all of them had blanket rule no new features live in this db. whatever t
by foolfoolz 5y ago
this sounds backwards. i’ve worked at multiple places with the one big legacy mysql db. all of them had blanket rule no new features live in this db. whatever this complicates you would design around it
- MrStonedOne 5y ago
- taywrobel 5y agoLive in the DB and use data from the DB are two separate things. Packages has its own dedicated MySQL cluster for all package related info. Auth also lives in a separate database. But it still needs to access org or repo information in many use cases.
- 8n4vidtmkvmk 5y agoat my company we just migrate away from old tech at ridiculous cost. back to back 2 years migrations. weeee
- foolfoolz 5y agowhat would you rather have, 2 year of migrations or having production incidents daily?
- 8n4vidtmkvmk 5y agoI'm not sure they're increasing production stability.. every migration results in several post mortems
- masklinn 5y agoThe new features don’t live in that cluster, but they have to interact with it as it holds all of the core stuff. E.g. codespaces is literally a web IDE, so extensively interacting with repositories and accounts would be involved in pretty much all if its tasks.