![Revisit consent button](../images/body-df29beacd7496220cc94.svg) We value your privacy We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies. Customise Reject All Accept All Customise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg) We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below. The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more NecessaryAlways Active Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. * Cookie BCTempID * Duration 10 minutes * Description No description available. * Cookie __cf_bm * Duration 1 hour * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie AWSALBCORS * Duration 7 days * Description Amazon Web Services set this cookie for load balancing. * Cookie _cfuvid * Duration session * Description Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services * Cookie li_gc * Duration 6 months * Description Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. * Cookie __hssrc * Duration session * Description This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. * Cookie __hssc * Duration 1 hour * Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. * Cookie wpEmojiSettingsSupports * Duration session * Description WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. * Cookie BCSessionID * Duration 1 year 1 month 4 days * Description Blueconic sets this cookie as a unique identifier for the BlueConic profile. * Cookie _octo * Duration 1 year * Description No description available. * Cookie logged_in * Duration 1 year * Description No description available. * Cookie __Secure-YEC * Duration past * Description YouTube sets this cookie to stores the user's video player preferences using embedded YouTube video * Cookie __eoi * Duration 6 months * Description Description is currently not available. * Cookie AWSALBTGCORS * Duration 7 days * Description No description available. * Cookie login-status-p * Duration past * Description Description is currently not available. * Cookie AWSALBTG * Duration 7 days * Description No description available. * Cookie csrf_token * Duration session * Description No description available. * Cookie token_v2 * Duration 1 day * Description Description is currently not available. * Cookie D * Duration 1 year * Description Description is currently not available. * Cookie PHPSESSID * Duration session * Description This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. * Cookie VISITOR_PRIVACY_METADATA * Duration 6 months * Description YouTube sets this cookie to store the user's cookie consent state for the current domain. * Cookie cookietest * Duration session * Description The cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience. * Cookie __Host-airtable-session * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie __Host-airtable-session.sig * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie m * Duration 1 year 1 month 4 days * Description Stripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly. * Cookie BIGipServer* * Duration session * Description Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. * Cookie __cfruid * Duration session * Description Cloudflare sets this cookie to identify trusted web traffic. * Cookie _GRECAPTCHA * Duration 6 months * Description Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. * Cookie __Secure-YNID * Duration 6 months * Description Google cookie used to protect user security and prevent fraud, especially during the login process. * Cookie cookieyes-consent * Duration 1 year * Description CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors. Functional Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features. * Cookie lidc * Duration 1 day * Description LinkedIn sets the lidc cookie to facilitate data center selection. * Cookie brw * Duration 1 year * Description No description available. * Cookie brwConsent * Duration 5 minutes * Description Description is currently not available. * Cookie WMF-Uniq * Duration 1 year * Description Description is currently not available. * Cookie loom_anon_comment * Duration 1 year * Description No description available. * Cookie loom_referral_video * Duration session * Description Description is currently not available. * Cookie VISITOR_INFO1_LIVE * Duration 6 months * Description A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. * Cookie yt-remote-connected-devices * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie ytidb::LAST_RESULT_ENTRY_KEY * Duration Never Expires * Description The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. * Cookie yt-remote-device-id * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie yt-remote-session-name * Duration session * Description The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. * Cookie yt-remote-fast-check-period * Duration session * Description The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. * Cookie yt-remote-session-app * Duration session * Description The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. * Cookie yt-remote-cast-available * Duration session * Description The yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player. * Cookie yt-remote-cast-installed * Duration session * Description The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. * Cookie cp_session * Duration 3 months * Description Codepen sets this cookie for Help systems found in the website. * Cookie loid * Duration 1 year 1 month 4 days * Description This cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform. Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc. * Cookie __hstc * Duration 6 months * Description Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). * Cookie hubspotutk * Duration 6 months * Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. * Cookie _ga * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. * Cookie _ga_* * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to store and count page views. * Cookie __Host-psifi.analyticsTrace * Duration 6 hours * Description Description is currently not available. * Cookie __Host-psifi.analyticsTraceV2 * Duration 6 hours * Description Description is currently not available. * Cookie _gh_sess * Duration session * Description GitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form. * Cookie YSC * Duration session * Description YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. * Cookie ajs_anonymous_id * Duration 1 year * Description This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. * Cookie vuid * Duration 1 year 1 month 4 days * Description Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. Performance Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors. * Cookie AWSALB * Duration 7 days * Description AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. * Cookie acq * Duration past * Description Description is currently not available. * Cookie acq.sig * Duration past * Description Description is currently not available. * Cookie ptc * Duration 2 years * Description No description available. Advertisement Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns. * Cookie muc_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to collect user behaviour and interaction data to optimize the website. * Cookie guest_id_marketing * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie guest_id_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie personalization_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. * Cookie guest_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences. * Cookie bcookie * Duration 1 year * Description LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. * Cookie __Secure-ROLLOUT_TOKEN * Duration 6 months * Description YouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment. * Cookie yt.innertube::nextId * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie yt.innertube::requests * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie session_tracker * Duration session * Description This cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website. * Cookie edgebucket * Duration session * Description Reddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content. * Cookie did * Duration 1 year * Description Arbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year. Uncategorised Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet. No cookies to display. Reject All Save My Preferences Accept All Toggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation [](https://towardsdatascience.com/) Publish AI, ML & data-science insights to a global community of data professionals. Sign in[Submit an Article](https://write.insightmediagroup.io) [Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/) * * * [Write For TDS](https://towardsdatascience.com/submissions/) [LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) # I Tried to Schedule My ETL Pipeline. Here’s What I Didn’t Expect. What I thought was a scheduling problem turned out to be a portability problem first [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) June 19, 20267 min read ![](../images/000.jpg) Generated by Gemini AI In my last article, I mentioned that scheduling is the next wall I'll be walking toward. So I guess, here I am, walking towards it But before I get into what happened, let me give some context for anyone stumbling on this for the first time. I am a systems analyst who decided to transition into data engineering. Instead of just taking courses and collecting certificates, I decided to learn by building and writing about it publicly. Every article in this series documents something I actually built, the decisions I made, the things that broke, and what I learned from it. The first article was [my 12-month self-study roadmap](https://towardsdatascience.com/from-data-analyst-to-data-engineer-my-12-month-self-study-roadmap/), where I laid out the plan for how I was going to approach this transition. The second was me [building my first ETL pipeline from scratch](https://towardsdatascience.com/i-built-my-first-etl-pipeline-as-a-complete-beginner-heres-exactly-how/) using the GitHub API, as a complete beginner. In the third, I took that same pipeline and [made it more production-ready](https://towardsdatascience.com/i-thought-data-engineering-was-just-writing-scripts-i-was-wrong/) by adding SQLite storage, idempotency handling, and Google Drive persistence, all inside Google Colab. This article is the fourth. And it picks up exactly where the last one ended. I expected to spend most of my time picking a scheduling tool and configuring it. What I didn't expect was that before I could even think about scheduling, I had to deal with something more fundamental. My pipeline couldn't run outside of Google Colab. And until that changed, no scheduler in the world could help me. This is the story of what actually happened. Learn this step by step with the interactive [Data Engineer](https://roadmap.sh/data-engineer) roadmap. ## The First Wall: My Pipeline Lived in Colab Before I even got to scheduling, I wanted to understand what it would actually take to run my pipeline automatically. So I looked at my code properly for the first time with that question in mind. Here's what the load section looked like: python ``` conn = sqlite3.connect('/content/drive/MyDrive/github_repos.db') ``` That path, `/content/drive/MyDrive/`, only exists inside Google Colab. It's the mounted Google Drive path that Colab gives you when you connect your Drive to a notebook. Outside Colab, that path doesn't exist. If any scheduler tried to run this script, it would crash right there. The interesting thing is that my code had no `google.colab` imports. No Colab-specific libraries. Just one hardcoded path that I had been typing without really thinking about it. That path was the dependency, not the code. This was the first thing I didn't expect. I thought the challenge would be learning a scheduling tool. Instead, the first lesson was that my environment was part of my pipeline, and I hadn't noticed. The fix was simple. Instead of hardcoding the Colab path, I made the database path configurable through an environment variable: python ``` import os DB_PATH = os.environ.get('DB_PATH', 'github_repos.db') conn = sqlite3.connect(DB_PATH) ``` Now the script uses whatever path is set in the environment. If nothing is set, it falls back to creating a local `github_repos.db` file in the same folder. One change, and the pipeline was no longer tied to Colab. ## Running It Outside Colab for the First Time Before setting up any scheduler, I wanted to confirm the script actually worked on its own. So I saved it as `pipeline.py`, created a `requirements.txt` with the two libraries it needs: text ``` requests pandas ``` And ran it from my terminal: It printed: `Pipeline complete. Duplicates handled.` And a file called `github_repos.db` appeared in my folder. The same pipeline I had been running in Colab was now running as a plain Python script, anywhere. That felt like a bigger deal than I expected. Not because the change was complex, it wasn't. But because I realized I had been thinking of my pipeline as a notebook, when what I actually had was a script that happened to live inside one. ## Choosing a Scheduling Tool At this point I had a standalone script. Now I needed something to run it on a schedule. I looked at a few options. APScheduler lets you define schedules inside your Python code, which works while a session is running but stops the moment you close your terminal. That's not really scheduling, that's just a loop. Airflow is the industry standard for orchestrating pipelines, but it requires running a server, a metadata database, and a web interface. That's a lot of infrastructure for where I am right now. GitHub Actions sat in the middle. It's free, it runs on GitHub's servers, the schedule is defined in code, and it doesn't require me to maintain any infrastructure. The tradeoff is that it's designed for CI/CD workflows, not pipeline orchestration, so it has limits around complex dependencies and monitoring. But for a pipeline at my stage, it's a practical choice. I also want to be honest: tools like Airflow exist for a reason. When a pipeline grows, when you have dependencies between tasks, when you need visibility into what ran and what failed, you need proper orchestration. GitHub Actions is not that. But it's a good first step, and understanding why it's limited is part of learning what those more serious tools are actually solving. ## Setting Up GitHub Actions GitHub Actions works through workflow files, which are YAML files you place in a specific folder in your repository. The folder structure looks like this: text ``` github-etl/ ├── .github/ │ └── workflows/ │ └── schedule.yml ├── pipeline.py └── requirements.txt ``` Here's the full workflow file I created: yaml ``` name: Run ETL Pipeline on: schedule: - cron: '0 9 * * *' workflow_dispatch: jobs: run-pipeline: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: python-version: '3.11' - name: Install dependencies run: pip install -r requirements.txt - name: Run pipeline run: python pipeline.py ``` Let me walk through what each part is doing. * `cron: '0 9 * * *'` is the actual schedule. Cron is a time-based job scheduling format that's been around in Unix systems for decades. The five values represent minute, hour, day of month, month, and day of week. So `0 9 * * *` means: at minute 0 of hour 9, every day, every month, every day of the week. In other words, 9am UTC every day. * `workflow_dispatch` adds a manual trigger. This means you can also run the workflow by clicking a button in GitHub, without waiting for the scheduled time. This is useful for testing. * `runs-on: ubuntu-latest` tells GitHub to spin up a fresh Linux machine for each run. Every time the workflow triggers, GitHub creates a clean environment, installs your dependencies, runs your script, and then shuts everything down. There's no persistent machine sitting somewhere running your code. It's ephemeral. The steps are straightforward. Checkout pulls your code from the repository into the runner. Setup Python installs the version you specify. Install dependencies runs `pip install -r requirements.txt`. And then Run pipeline executes your script. ## What Happened When I Ran It After pushing the workflow file to GitHub, I went to the Actions tab in my repository and triggered it manually using the workflow_dispatch button. It ran. Twenty-seven seconds from start to finish. The pipeline pulled data from the GitHub API, transformed it, and loaded it into SQLite, all on a GitHub server, without me doing anything after clicking the button. I did get one warning on the first run: text ``` Node.js 20 actions are deprecated... ``` This was because I had used older versions of the checkout and setup-python actions. The fix was updating `actions/checkout@v3` to `actions/checkout@v4` and `actions/setup-python@v4` to `actions/setup-python@v5`. After that, the workflow ran clean. ## What I Actually Learned Going into this, I thought scheduling was about picking the right tool. What I found was that scheduling forced me to think about something I hadn't thought carefully about before: portability. A pipeline that only runs in one specific environment isn't really a pipeline. It's a script tied to a platform. Making it schedulable meant making it portable first, and making it portable meant understanding what it actually depended on. The hardcoded path was a small thing. But catching it changed how I think about writing pipeline code going forward. Every time I write a path or a credential or an environment-specific value, I now ask whether that thing will exist outside the context I'm building in. The other thing I learned is that scheduling and orchestration are different problems. GitHub Actions handles scheduling well. It doesn't handle things like retrying failed runs with backoff, alerting when something goes wrong, visualizing pipeline dependencies, or managing multiple pipelines that depend on each other. Those are orchestration problems, and they're what tools like Airflow are built to solve. I'm not there yet. But I understand now why those tools exist in a way I didn't before. ## What's Next The pipeline is now running every day at 9am UTC. Data is being collected. And I'm starting to notice something: when you have a pipeline running daily, you start caring about the data it produces in a different way. Are all the records clean? Are there repos slipping through with missing fields? Is the viral flag actually meaningful, or did I define it in a way that makes almost everything "No"? Those are data quality questions. And they're the next wall I'm walking toward. _This is part of my ongoing series documenting my transition from systems analyst to data engineer. If you've been following along, thank you. If this is your first article in the series, the earlier ones are linked below._ [From Data Analyst to Data Engineer: My 12-Month Self-Study Roadmap](https://towardsdatascience.com/from-data-analyst-to-data-engineer-my-12-month-self-study-roadmap/) [I Built My First ETL Pipeline as a Complete Beginner. Here’s How.](https://towardsdatascience.com/i-built-my-first-etl-pipeline-as-a-complete-beginner-heres-exactly-how/) [I Thought Data Engineering Was Just Writing Scripts. I Was Wrong.](https://towardsdatascience.com/i-thought-data-engineering-was-just-writing-scripts-i-was-wrong/) _Connect with me on_[ _LinkedIn_](https://www.linkedin.com/in/ibrahim-salami-059863228/) _,_[_YouTube_](https://www.youtube.com/@ibbysalam) _, and_[ _Twitter_](https://x.com/IbbySalam) _._ ## Register Now to Continue Reading ### Unlock Towards Data Science with a Free Account All articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more. Register for freeSign in to your account * * * ![](../images/body-542334df68a32cd56c4a.jpeg) Written By ## [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) [See all from Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) [Data Engineer](https://towardsdatascience.com/tag/data-engineer/)[Data Pipeline](https://towardsdatascience.com/tag/data-pipeline/)[Data Science](https://towardsdatascience.com/tag/data-science/)[Etl](https://towardsdatascience.com/tag/etl/)[Google Colab](https://towardsdatascience.com/tag/google-colab/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fi-tried-to-schedule-my-etl-pipeline-heres-what-i-didnt-expect%2F&title=I%20Tried%20to%20Schedule%20My%20ETL%20Pipeline.%20Here%E2%80%99s%20What%20I%20Didn%E2%80%99t%20Expect.) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fi-tried-to-schedule-my-etl-pipeline-heres-what-i-didnt-expect%2F&title=I%20Tried%20to%20Schedule%20My%20ETL%20Pipeline.%20Here%E2%80%99s%20What%20I%20Didn%E2%80%99t%20Expect.) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fi-tried-to-schedule-my-etl-pipeline-heres-what-i-didnt-expect%2F&text=I%20Tried%20to%20Schedule%20My%20ETL%20Pipeline.%20Here%E2%80%99s%20What%20I%20Didn%E2%80%99t%20Expect.) Towards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program. [Write for TDS](https://towardsdatascience.com/submissions/) ## Related Articles * [![](../images/001.jpg)](https://towardsdatascience.com/mapreduce-how-it-powers-scalable-data-processing/) ## [MapReduce: How It Powers Scalable Data Processing](https://towardsdatascience.com/mapreduce-how-it-powers-scalable-data-processing/) [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) An overview of the MapReduce programming model and how it can be used to optimize large-scale data processing. [Jimin Kang](https://towardsdatascience.com/author/jimin.kang821/) April 22, 202512 min read * [![](../images/002.jpeg)](https://towardsdatascience.com/how-to-expose-delta-tables-via-rest-apis-53b4dd7afa4e/) ## [How to Expose Delta Tables via REST APIs](https://towardsdatascience.com/how-to-expose-delta-tables-via-rest-apis-53b4dd7afa4e/) [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) Three architectures discussed and tested to serve delta tables [René Bremer](https://towardsdatascience.com/author/rebremer/) May 6, 20247 min read * [![](../images/003.jpg)](https://towardsdatascience.com/5-python-mistakes-you-should-avoid-12104e350030/) ## [5 Python Mistakes You Should Avoid](https://towardsdatascience.com/5-python-mistakes-you-should-avoid-12104e350030/) [Programming](https://towardsdatascience.com/category/programming/) Some of the most common bugs are hard to find [Pranjal Saxena](https://towardsdatascience.com/author/pranjalai/) September 2, 20224 min read * [![](../images/004.jpg)](https://towardsdatascience.com/create-your-first-cronjob-on-the-linux-server-74e2fdc76e78/) ## [Getting Started with Cron Job in the Linux Server: A Complete Tutorial for Beginner](https://towardsdatascience.com/create-your-first-cronjob-on-the-linux-server-74e2fdc76e78/) [Programming](https://towardsdatascience.com/category/programming/) Automate your regular job using cron [Audhi Aprilliant](https://towardsdatascience.com/author/audhiaprilliant/) November 11, 20205 min read * [![](../images/005.jpg)](https://towardsdatascience.com/streaming-in-data-engineering-2bb2b9b3b603/) ## [Streaming in Data Engineering](https://towardsdatascience.com/streaming-in-data-engineering-2bb2b9b3b603/) [Data Science](https://towardsdatascience.com/category/data-science/) Streaming data pipelines and real-time analytics [Mike Shakhomirov](https://towardsdatascience.com/author/mshakhomirov/) December 12, 20239 min read * [![](../images/006.jpg)](https://towardsdatascience.com/data-where-engineering-and-science-meet-296f54131752/) ## [Data: Where Engineering and Science Meet](https://towardsdatascience.com/data-where-engineering-and-science-meet-296f54131752/) [Data Science](https://towardsdatascience.com/category/data-science/) Our weekly selection of must-read Editors' Picks and original features [TDS Editors](https://towardsdatascience.com/author/towardsdatascience/) September 29, 20223 min read * [![](../images/007.jpg)](https://towardsdatascience.com/feature-engineering-with-microsoft-fabric-and-pyspark-16d458018744/) ## [Feature Engineering with Microsoft Fabric and PySpark](https://towardsdatascience.com/feature-engineering-with-microsoft-fabric-and-pyspark-16d458018744/) [Data Science](https://towardsdatascience.com/category/data-science/) Fabric Madness part 2 [Roger Noble](https://towardsdatascience.com/author/roger_noble/) April 8, 202413 min read * [![](../images/008.png)](https://towardsdatascience.com/data-engineering-a-formula-1-inspired-guide-for-beginners-5511488803ee/) ## [Data Engineering: A Formula 1-inspired Guide for Beginners](https://towardsdatascience.com/data-engineering-a-formula-1-inspired-guide-for-beginners-5511488803ee/) [Data Engineering](https://towardsdatascience.com/category/data-science/data-engineering/) A Glossary with Use Cases for First-Timers in Data Engineering [Matteo Consoli](https://towardsdatascience.com/author/matteo-consoli/) December 4, 20236 min read * [![](../images/009.png)](https://towardsdatascience.com/2020-nfl-postseason-predictions-from-machine-learning-model-super-bowl-d5d7804e26ae/) ## [2020 NFL Postseason Predictions from Machine Learning Model - Super Bowl](https://towardsdatascience.com/2020-nfl-postseason-predictions-from-machine-learning-model-super-bowl-d5d7804e26ae/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Chiefs are 1-2 point favorite, but model might be undervaluing Chiefs offense [Nasir Bhanpuri, PhD](https://towardsdatascience.com/author/nasir-bhanpuri/) February 6, 20214 min read * [YouTube](https://www.youtube.com/c/TowardsDataScience) * [X](https://x.com/TDataScience) * [LinkedIn](https://www.linkedin.com/company/towards-data-science/) * [Threads](https://www.threads.net/@towardsdatascience) * [Bluesky](https://bsky.app/profile/towardsdatascience.com) [](https://towardsdatascience.com/) Your home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals. Subscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/) © Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network) #### Recommended Articles Close * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ "Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ "The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ "Does Your Company Have a Data Strategy?") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/4970/image?etag=1780565225463&width=500&height=500) Productivity Tips, Data Career Insights, and Other Recent Must-Reads ](https://towardsdatascience.com/productivity-tips-data-career-insights-and-other-recent-must-reads-5c47eb7a2fe0/ "Productivity Tips, Data Career Insights, and Other Recent Must-Reads")