Understanding Tasks

Tasks can be pretty handy when you get the hang of them. They allow you to define a sequence of operations that can be executed in a specific order, making it easier to manage complex workflows.

To better understand tasks, let's racap what we have done so far in the tutorial. We have created a database migration that allows us to replicate our application's database anytime we need to. We have also created a model that represents our data structure and allows us to interact with the database.

Now, we need a way to interact with our model and perform database operations. While the ultimate goal of this tutorial is to create a RESTful APIs to do exactly that, let's first explore a different approach of interacting with our application code using tasks.

Creating a Task

Coming Soon...

Mandatory arguments

Coming Soon...

Use-Cases

Tasks can be used in various scenarios, such as:

• Performing data transformations
• Running cronjobs or background jobs
• Generating reports or performing data analysis
• Automating repetitive tasks
• Running a data cleanup job

The list goes on, but the key takeaway is that tasks are a powerful tool for automating and managing complex workflows in your application. And it's important to note that tasks are executables that can be run independently of your http application, which means you can run them in a separate process, container or even on a different machine.

Storing your first contact

Coming Soon...