rq-scheduler
packwerk
Our great sponsors
rq-scheduler | packwerk | |
---|---|---|
4 | 16 | |
1,386 | 1,494 | |
1.1% | 2.7% | |
2.2 | 7.6 | |
about 2 months ago | 15 days ago | |
Python | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rq-scheduler
- Keep the Monolith, but Split the Workloads
-
RQ-Scheduler for tasks in far future?
RQ-Scheduler is another simpler alternative (rq/rq-scheduler: A lightweight library that adds job scheduling capabilities to RQ (Redis Queue) (github.com)) that appears to be good for such purposes. It's not immediately clear if it would suffer from the same issues, but it seems not (Redis manages issues with data loss well, a separate queue is used for the scheduled tasks, etc.). Is anyone aware of any drawbacks to using RQ-Scheduler for something like this?
- Need direction on how to add asynchronous / scheduled tasks on my flask app running on aws beanstalk
-
Some advice: will my setup be production ready?
Some thoughts: - Storing API keys in Redis with AOF and RDB persistence turned on is going to be way faster than storing those keys in Mongo. - Did you mean RQ (redis-queue)/django-rq? If so, it works well as long as you don't need a scheduler for cron-like tasks, which it doesn't include. You can add rq-scheduler for that though: https://github.com/rq/rq-scheduler - Make sure your redis instance has a password -- redis 6 supports ACLs as well - The problem with slow requests is that they tie up app server processes and usually also database connections. That may be fine with a small number of consumers, but if you point your web site at this API, you may run into problems. Consider that if an app server serving web site traffic is waiting for a slow request to your API, then both app servers are affected -- you're now holding resources on the web site and the API, effectively. - HTTP clients often use a default timeout value for requests, and it's a best practice to use such a timeout -- so you'll need to coach your partners consuming this API not to use timeouts for your API.
packwerk
-
Must-have gems for mature Rails
gem "packwerk" - https://github.com/Shopify/packwerk | Allows modularising Ruby code, a must-have for growing projects.
-
Keep the Monolith, but Split the Workloads
Yep, that article is about very similar concepts but grounded in Spring as the framework.
I like what they do around package imports and it looks a lot like what we do at incident.io, with some rules about which packages can import what.
For people in the Ruby world who want a similar solution, Shopify provide an open-source framework called packwerk that is designed just for this:
https://github.com/Shopify/packwerk
-
All you need is Rails (Engines): Compartmentalising your Monolith
Iād probably go with packwerk before rails engines these days
-
How to break up a rails monolith
https://github.com/Shopify/packwerk allows you to make dependencies between components explicit
- Best way to go about fragmenting a Monolithic Rails application into Microservices.
-
OOP vs. services for organizing business logic: is there a third way?
Packwerk ā to enforce boundaries and modularize Rails applications
-
Organizing Rails files by meaning
Take a look at Packwerk from some folks at Shopify - gets you the benefits of naming some components for organizing boundaries in your code, with each component having the usual rails folder structure, but without the hard isolation restrictions of doing so with Engines.
-
How to edit a model from another controller
Nothing is stopping you from doing so except you (and maybe packwerk, but you very likely don't have that installed).
-
The advent of tooling for Big Rails
For me, the most important aspect of a growing Rails app is handling of complexity and interdependencies and turns out Shopify's packwerk is just what the doctor ordered - it leverages zeitwerk loader to improve on Rails' vanilla file structure, allowing to group files by business concept or sub-domain and control visibility and ownership.
-
Exploring DryRB - Intuition of Results
Let's set the stage right quick. You happen to be in a large Rails application that follows along with something like Packwerk to clearly delineate different packages in your Rails monolith. Let's say you have 100 packs, which is not particularly unusual with larger applications.
What are some alternatives?
fastapi-cloud-tasks - GCP's Cloud Tasks + Cloud Scheduler + FastAPI = Partial replacement for celery.
Solidus - š Solidus, the open-source eCommerce framework for industry trailblazers.
django-rq - A simple app that provides django integration for RQ (Redis Queue)
appmap-ruby - AppMap client agent for Ruby
celery - Distributed Task Queue (development branch)
Flask-RQ2 - A Flask extension for RQ.
whitehall - Publishes government content on GOV.UK
django-rq - A simple app that provides django integration for RQ (Redis Queue) [Moved to: https://github.com/rq/django-rq]
suture - š„ A Ruby gem that helps you refactor your legacy code
supervisor - Supervisor process control system for Unix (supervisord)
gitlab