If you’re not building with AI, are you even building these days? Sometimes, it seems not. AI has become such an integral part of workflows throughout many tools that a clear understanding of integrating it into your product and framework is critical. Django is such a framework that powers thousands of products across the web: Instagram, Pinterest, and Mozilla are all services built on Django.

Background job processing is integral to modern software architecture. Background jobs allow resource-intensive tasks to be handled asynchronously, improving your application’s responsiveness and efficiency. You can use background processing for tasks such as sending emails, data processing, and batch jobs. If you were to run these synchronously, they could significantly degrade the user experience and system performance. Thus, most frameworks have libraries for running background jobs.

After Twitter moved from Ruby to Scala in 2009, the story was born that Ruby on Rails can’t scale. The story goes that it lacks robustness, is a memory hog, and lacks the concurrency features you need to grow an application. This has been the prevailing wisdom for over a decade. And then along came Shopify, showing that, as Lutke says, Ruby on Rails is a framework that can process billions of events per day and evidently does scale. Ruby on Rails is an excellent candidate for scaling.