3 ms·
Deciding between a tech that you already know and know will work well for the problem, and a tech you don't know - that's an easy choice. A harder choice is wh
by Buttons840 6y ago
Deciding between a tech that you already know and know will work well for the problem, and a tech you don't know - that's an easy choice.
A harder choice is when you know the tech you known doesn't quite fit. Do you go with what you know, or do you try something new?
Concrete example I'm currently considering: If I want to make a web pages that does some background work, should I use Django and Celery like last time, and spend months tweaking Celery settings I don't understand and still feel like the system's kinda clunky (like last time). Or do I use Elixir where there's little difference between handling a HTTP request and running a background task, and where I can just spin up a few thousand threads to monitor background tasks?
TLDR: What do you do when "what you know best" isn't the right choice?
- jacquesm 6y agoWebpages that do background work will need something client side, not server side. Javascript + a timer to kick things off periodically should be enough for that. Unless I'm misunderstanding what you mean by 'background work'.
- deleted 6y ago[deleted]
- nomdep 6y agoYou could research for some altermatives in the same space instead of repoacing the whole stack. For example, dramatiq and python-rq are simpler to configure and to work with than the helicopter-level-of-complexity that is Celery.