I love how you explain exactly what the deal is regarding synchronous requests, and explain exactly what Sidekiq would be used for. A big problem I have is running into tools and libraries that sound interesting, but I can't exactly figure out what they do, or why they'd help me because of all the jargon that everyone assumes you already know.
Great tutorial! I think that the fact that you show your face makes you connect more with viewers, and you're the first web developer with a youtube channel that i've seen doing it. :) Keep it up!
Thank you!! I've been having a problem and the worst part is knowing it's running but doesn't know what's the logic error but thanks to the UI, I finally know why it's not doing what I want it to do.
Fantastic video. Thanks for starting all the way from the beginning and going all the way to production. One question: If I have multiple workers, do I need to put multiple workers in my procfile?
"This youtube channel is about to BLOW THE FUCK UP" lmfao - but yeah this video was awesome, thank you for creating! ONE QUESTION/SUGGESTION... It would be helpful to make a list of common scenarios and how to set up threads to process those scenarios properly. For example. Simple Scenario: "Creating a user/report (like this video explains)", Heavy Duty Scenario: "Scheduling 20 drip emails when a user opts-in at scale at 100 user opt-ins per minute"
Thanks a ton for this video! Does this need a paid account for Heroku? Or can an app run multiple dynos for these web and worker processes with the free version?
Yo Jordan, great video. I was curious why you didn't need to start a redis server on heroku, and just a sidekiq one? Does the redis gem take care of that for us?
But you don't show how to access the report once it's generated! Not to mention that multiple users can generate multiple reports, each with different parameters...how are they supposed to view their reports once the associated background job is completed?
Hey, great video! I had to learn from LOTS of different places this very same information that you just put into one video, good job! From my own experience, I had to move from RedisToGo to RedisCloud (also free) because I kept getting a Max number of connections reached error. Looks like RedisCloud offers 30 connections and for some reason my simple email worker created up to 27 connections. So bottom line: can you make a video about configuring your application/ job back-end/ Heroku so that you can get optimal number of connections? That's the only piece of information I just couldn't get and looks like the default configuration wasn't helping. Thanks again, David
@decipherMedia or @anyone Please answer this, Question: But once the report is generated how do you return it back to the client? How does a background job still Fulfil the clients needs? Any idea how to come around this?
If I'm doing this in the context of a ReactApp, is there a NodeJS approach for doing this? If so, is there a reason to opt for the Rails approach instead?
You didn't show how to access the message from the queue (aka retrieve the report). That's the reason real apps need to use sidekiq with redis to begin with.
Very educative, as usual, thanks for the video. Can I make a request for Angular 2/Rails 5 tutorial, with best practices, running and deploying to production environments. I was thinking about something like a simple Angular 2 CRUD app with a REST Client running on a simple stand alone web server, and a Rails 5 backend server in --api mode, handling the requests of the NG2 app, the ideal would be to make them communicate securely with something like jwt? involving action cable would be a huge plus. What do you think? I'll make a diagram once i get home, and now that I have more free time, I'll finally start working on a proof of concept, hit me up of interested, we could build this together.
