Why I believe Rails is still relevant in 2019

Re:Why I believe Rails is still relevant in 2019 by rememberlenny on Tuesday March 19, 2019 @02:00PM (#19433540)

Just to share for anyone interested in the Rails gems I'm using.

An asynchronous worker manager is helpful for handling cron jobs, mail tasks, and various batch processes that can be loaded into memory (mostly Redis) but processed later.

I use the gem Sidekiq which, as is, provides a UI and API that I rely heavily on. I might just not know the best practices, but I definitely find this valuable.

The BI tools are not something found in most ecosystems. Not to mention dead simple setup. I use two gems, Ahoy and Blazer, which together provide a simple API for event tracking and saving database queries.

[1]: https://sidekiq.org/

[2]: https://github.com/ankane/ahoy

[3]: https://github.com/ankane/blazer

[ Parent | on HN ]

Re:Why I believe Rails is still relevant in 2019 by gumcreme on Tuesday March 19, 2019 @02:32PM (#19433975)

I know what an async worker and what sidekiq is. But apparently you don't know that in modern stacks you don't need this anymore and it was an oddity because of RoR.

I am on mobile and don't have time to write down why, please just go to StackOverflow and ask people why something like Sidekiq is not needed in stack x.

[ Parent | on HN ]

Re:Why I believe Rails is still relevant in 2019 by qnsi on Tuesday March 19, 2019 @02:52PM (#19434262)

What stack would you recommend if not rails? Serious question with no malice

[ Parent | on HN ]

Re:Why I believe Rails is still relevant in 2019 by nitrogen on Wednesday March 20, 2019 @01:39AM (#19439322)

I'm currently working in the JVM and find myself wishing I had Sidekiq. Learn at least two stacks to some degree so you can contrast and know what you are missing when you inevitably have to learn a third and a fourth and a fifth.

[ Parent | on HN ]