Ask HN: When does it make sense to roll your own X?

Re:Ask HN: When does it make sense to roll your own X? by michaelcampbell on Sunday July 14, 2019 @08:39AM (#20433063)

We've had a lot of mysterious "it just stops working" issues with Celery, and their # of open tickets is approaching scary levels.

Moving everything to rq, and so far so good.

[ Parent | on HN ]

Re:Ask HN: When does it make sense to roll your own X? by withinboredom on Sunday July 14, 2019 @02:49PM (#20435126)

Are you sure that changing your implementation didn't fix a bug?

I've noticed that a lot of "dependency" problems on "complex systems" are usually programmer implementation problems. Changing the implementation forces you to review the original implementation (or throw it out) and fix the bug that caused you to change the implementation in the first place.

[ Parent | on HN ]

Re:Ask HN: When does it make sense to roll your own X? by orf on Sunday July 14, 2019 @08:47AM (#20433093)

We’ve had exactly the opposite experience. RQ was an absolute nightmare in every aspect across two companies I’ve worked at. And when you need something that Celery supports that RQ does not, you are in a pickle.

I wish you the best, but I cannot help but think you will regret that decision.

[ Parent | on HN ]

Re:Ask HN: When does it make sense to roll your own X? by orf on Sunday July 14, 2019 @11:07AM (#20433806)

Also, Kiwi.com gave a talk[1] about their experiences with RQ and how/why they migrated to Celery at EuroPython last week. It's worth a watch.

1. https://youtu.be/SUQYuA9AJT0?t=7546

[ Parent | on HN ]

Re:Ask HN: When does it make sense to roll your own X? by o-__-o on Sunday July 14, 2019 @12:21PM (#20434267)

Have never experienced this and we sold a huge number of our app using celery. Based on other replies one should pause, take a step back and consider if their code or design is to blame..

[ Parent | on HN ]