Adding content to 106-background-jobs

src/roadmaps/system-design/content/106-background-jobs/100-event-driven.md

@@ -1 +1,11 @@
-# Event Driven
+# Event Driven
+
+Event-driven architecture (EDA) is a design pattern that focuses on the flow of events through a system, rather than the flow of data or control. It is based on the idea that a system should respond to external events and trigger the appropriate actions.
+
+In an event-driven system, events are generated by external sources, such as user input, sensors, or other systems, and are passed through the system to be handled by the appropriate components. These events can trigger various actions, such as updating the state of the system, sending a message to another system, or triggering a computation.
+
+Learn more from the following links:
+
+- [What is an Event-Driven Architecture?](https://aws.amazon.com/event-driven-architecture/)
+- [Event-Driven Architecture - Everything You Need to Know](https://blog.hubspot.com/website/event-driven-architecture)
+- [System Design: Event-Driven Architecture (EDA)](https://dev.to/karanpratapsingh/system-design-event-driven-architecture-eda-3m72)

src/roadmaps/system-design/content/106-background-jobs/101-schedule-driven.md

@@ -1 +1,15 @@
-# Schedule driven
+# Schedule Driven
+
+Schedule-driven systems are systems that are designed to perform specific tasks or actions at predetermined times or intervals. These schedules can be defined by the system itself or can be set by an external agent, such as a user or another system.
+
+Examples of schedule-driven systems include:
+
+- Cron jobs
+- Scheduled batch jobs
+- Recurring events
+- Automated trading systems
+
+Learn more from the following links:
+
+- [System Design - Job Scheduling System?](https://aws.amazon.com/event-driven-architecture/)
+- [Scheduler System Design](https://atul-agrawal.medium.com/scheduler-as-a-service-9c5d0414ec6d)

src/roadmaps/system-design/content/106-background-jobs/102-returning-results.md

@@ -1 +1,7 @@
-# Returning results
+# Returning Results
+
+Returning results in a system design refers to the process of providing the output or outcome of a specific task or action to the requesting entity. This can include providing a response to a user request, returning a result of a computation or analysis, or sending a notification or message to another system.
+
+Learn more from the following links:
+
+- [Overview of Return Statement](https://press.rebus.community/programmingfundamentals/chapter/return-statement/)

src/roadmaps/system-design/content/106-background-jobs/index.md

@@ -1 +1,14 @@
-# Background jobs
+# Background Jobs
+
+Background jobs in system design refer to tasks that are executed in the background, independently of the main execution flow of the system. These tasks are typically initiated by the system itself, rather than by a user or another external agent.
+
+Background jobs can be used for a variety of purposes, such as:
+
+- Performing maintenance tasks: such as cleaning up old data, generating reports, or backing up the database.
+- Processing large volumes of data: such as data import, data export, or data transformation.
+- Sending notifications or messages: such as sending email notifications or push notifications to users.
+- Performing long-running computations: such as machine learning or data analysis.
+
+Learn more from the following links:
+
+- [Intro of Background job system](https://www.codementor.io/projects/tool/background-job-system-atx32exogo)