You should definitely write an article with all tricks you used to make it fast!

Thanks. I bought your book since the B1.0 version and I recommend it.

Thank you! Beta book period is nearly wrappped up!

Author here.

Thanks to all commenters for sharing their experiences and constructive opinions. It shows that this post is incomplete and far from being perfect. So, I just wrote a post-scriptum to improve it a bit for future readers.

https://alexis.bernard.io/blog/2023-10-15-background-job-que...

Thanks !

If that may interest someone and to do some self promotion too :-)

I have built a product (rails app monitoring service) that shows the file:line for each SQL request: https://rorvswild.com

I used them once, it's a good service. I prefer Scalingo over Heroku because there is no virtualisation layer.

2 simple lines in /etc/ssh/sshd_config fix the problem:

  PermitRootLogin no
  PasswordAuthentication no

I know I am preaching to the choir, but ANY login for any port or protocol should have rate limiting and non-default passwords.

Burp suite can easily crack web logins if you allow hundreds of logins per second for a single user.

I built it for myself to monitor my rails apps. I am aware several tools already exist, but not the one I was looking for.

I wanted a simple tool to pinpoint the slow SQL queries in my code. A tool that helps me taking care of my cron jobs and background jobs. A tool that does not send emails for errors I am already aware of.

If you have some time to give it a try, I would really appreciate your feedback. Thanks!

We built Teamodoro because we figured out that the Pomodoro techniques works well for individuals but not so much for a team. A team willing to use this technique must synchronize in order to prevent interruptions. Interruptions kill productivity and require a significant recovery period.

I'd love to get some feedback.

You have to do that choice on start because it's so annoying and a waste of time to do the switch later on. Particularly, that's definitely depends of your app. Is your app really heavy on the frontend side? If yes it's worth it to start with a frontend framework. Otherwise I prefer to have a traditional approach.