The latest articles on DEV Community by Guilherme Cavalcante (@gscdataanalytic). https://dev.to/gscdataanalytic https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3940424%2F95cbe02d-c71e-4b20-96f8-70e8a4ac0f69.jpeg https://dev.to/gscdataanalytic en Guilherme Cavalcante Tue, 19 May 2026 13:58:25 +0000 https://dev.to/gscdataanalytic/a-data-platform-tracking-news-and-social-media-across-167-cities-in-rio-grande-do-norte-for-under-5hh8 https://dev.to/gscdataanalytic/a-data-platform-tracking-news-and-social-media-across-167-cities-in-rio-grande-do-norte-for-under-5hh8 <p>I put a data pipeline into production paying 30x less than a traditional setup would require.</p> <p>Over the last few months, I built a platform that monitors all 167 municipalities in Rio Grande do Norte using data from news outlets, Facebook, Instagram, X, and TikTok. The data goes through Portuguese text processing, is served through a FastAPI API, and reaches a React dashboard almost in real time.</p> <p>What reduced the cost the most? Here it is:</p> <p>→ Cloud Run Jobs instead of keeping Airflow running 24/7. The container starts, runs the pipeline, and shuts down. Since processing takes only a few minutes and happens a few times a day, the bill practically disappears.<br> → Local DuckDB during development, BigQuery only in production. I can test everything without burning cloud quota.<br> → NLP without relying on LLMs for everything. I used spaCy with deterministic rules in Portuguese: fast, cheap, and auditable. LLMs only come in when someone asks for an explanation of specific content.<br> → Data Lake in Parquet before BigQuery. Reprocessing became trivial and raw data stays preserved.<br> → GitHub Actions authenticating to GCP through Workload Identity Federation with OIDC. Zero private keys stored in secrets.</p> <p>A lot of expensive architecture exists because copying tutorial stacks became a habit. Every project decision (and every alternative I discarded) is documented in the README.<br> Stack: Python, dbt, BigQuery, Terraform, GCP, FastAPI, React, TypeScript, spaCy, and uv workspace.</p> <p>Part of the development was done through pair programming with Claude Code. I make that explicit because the tool accelerates writing, but does not replace technical decision-making.</p> <p>More details, architecture, and dashboard: guilhermecavalcante.works<br> Open source: <a href="https://lnkd.in/da3ZZiZ3" rel="noopener noreferrer">https://lnkd.in/da3ZZiZ3</a></p> <p>I’m open to opportunities in Data Engineering, Analytics Engineering, and AI solutions.</p> <p>Question for people working with infrastructure and data: do you also feel that many stacks today already start oversized?</p> <h1> DataEngineering #AnalyticsEngineering #MLOps #Python #BigQuery #GCP </h1> dataengineering googlecloud python serverless