DEV Community

Juan Rueda
Juan Rueda

Posted on • Originally published at pepefeliblu.github.io on

Google DevFest Quito: A Journey into Modern Engineering

Google DevFest Badge
The volunteer got a bit nervous and skipped the 'n' in my name, so we had to perform a hot-fix and squish it in.

This past month, I attended Google DevFest Quito 2025 at Universidad San Francisco de Quito. While the event showcased the latest from Google, the real value lay in the architectural discussions that cut through the hype. It wasn't just about tools; it was about strategy.

Here are the key takeaways that are reshaping my perspective on modern engineering.

📊 Modern Data Architecture: Actionable vs. Just "Big"

Speaker: Erick Andre Naunay

The industry definition of "Big Data" is maturing. It's no longer just about hoarding terabytes; it's about shifting from "data without action" to data as a competitive advantage. If your data doesn't drive decisions in minutes, it's just a cost center.

The Shift to ELT

The classic ETL (Extract, Transform, Load) model is rigid and hard to scale. The modern approach is ELT (Extract, Load, Transform), where raw data lands first, and transformations happen within the warehouse.

  • Transformation Layer : Tools like dbt (data build tool) allow us to version, test, and document transformations like software code.
  • Orchestration : Mage AI was highlighted as a modern alternative for orchestrating pipelines, integrating seamlessly with Spark and monitoring tools.

The Medallion Architecture

To ensure quality, data should flow through distinct layers:

  1. Bronze : Raw data (Data Lake).
  2. Silver : Cleaned and filtered data.
  3. Gold : Business-level aggregates ready for consumption.

Crucially, Kimball modeling remains the gold standard for structuring this "Single Source of Truth," proving that foundational theory often outlasts trend cycles.

🧠 Agentic AI & The Local Web

Speakers: Braulio Otavalo & Erick Wendel

We are moving past the era of simple chatbots into Agentic AI , systems with memory, reasoning, and tool access. But the most interesting shift isn't in the cloud; it's in the browser.

The Browser as an AI Runtime

Erick Wendel demonstrated that the web is evolving. With Chrome's built-in AI APIs, we can run LLMs locally. This solves two massive problems: Privacy (data never leaves the device) and Cost (no per-token fees).

Small Language Models (SLMs)

The future is likely Small Language Models. They are operational, cost-effective, and fast. While they struggle with the O(n^2) complexity of transformers, for specific tasks, they blow massive models out of the water in terms of ROI.

Other notables: Model Context Protocol (MCP) for standardizing tool access, and llms.txt as the new robots.txt for AI crawlers.

⚙️ Infrastructure as Code: Foundational, Not Optional

Speakers: Luis Carlos Reyes Vanegas & Camilla Martins

In 2024, "click-ops" is technical debt. Scalability, security, and maintainability must be baked in from day one.

The winning formula presented was IaC + AI + Google Cloud :

  • Terraform: Provides the immutability and state management required for team collaboration.
  • Traceability : Every change is versioned. If it's not in code, it doesn't exist.
  • Environment Parity : Creating exact replicas of Prod in QA and Dev environments becomes trivial, reducing the "it works on my machine" syndrome.

🎨 Domain Driven Design: Organization as Code

Speaker: Tex Albuja

DDD is often treated as abstract theory, but Tex framed it as an organizational necessity. The biggest challenge in product teams isn't coding; it's communication.

Event Storming

The highlight was a practical approach to Event Storming using a standardized color code for sticky notes:

  • Orange : Domain Events (Past tense verbs, e.g., OrderPlaced).
  • Pink : Problems/Risks.
  • Blue : Commands (Imperative, e.g., PlaceOrder).

This visual language allows the design to "emerge" naturally. By clearly defining Bounded Contexts , we ensure that changes in one domain (e.g., Shipping) don't ripple out and break another (e.g., Billing). It’s about keeping systems decoupled and maintainable.


Thanks to the GDG Quito team for hosting such a high-signal event. It’s exciting to see the local community converging on these global best practices.

Top comments (0)