3 ms·
Just curious, what was the reason that your team decided to work around the problem instead of migrating away from MongoDB?
by hintymad 6y ago
Just curious, what was the reason that your team decided to work around the problem instead of migrating away from MongoDB?
- capableweb 6y agoNot the author but done similar things (patching something rather than migrating away from it). Usually it's way more work to migrate away than just patching it again to fit your use-case. Once you find yourself having to patch it too often, you start thinking about migrating away. Then the research slowly begins ad-hoc until it hits "seems we need to migrate away now, otherwise we're spending too much time working around something / fixing their broken shit", that's when you sit down and decide to migrate away from it. Also would depend on how long time you think the application will be around. You're building an MVP to evaluate something? Just hack together whatever will work (then throw away). You're maintain software for a library/archive that will most likely stick around for a long time, even if they say it's just temporary? Do decisions that will help in the future, always.
- inglor 6y agoWe have a complicated system and migration is ~3 months we won't be shipping features. We have a roadmap we need to meet and so far we have been trying to spill money on it rather than developers (paying mongo atlas) and adding features incrementally as Mongo gets them (like transactions). If this wasn't a startup we would probably rewrite.