[reClojure2025] Datomic at Nubank: Simplicity Scaled
Lecturer
Jordan Miller is a Staff Software Engineer at Nubank, where she is a core member of the Datomic team, specifically focusing on developer success and the evolution of the database product. Jordan is a prominent figure in the Clojure community, serving as the co-founder of Clojure Camp, a co-author of Clojure Brain Teasers, and the producer/host of the Lost In Lambduhhs podcast. Her professional background is marked by a deep passion for functional programming and a commitment to making complex technical systems accessible to a wider audience.
Abstract
Since its acquisition by Nubank in 2020, Datomic has transitioned from a specialized tool for discerning architects to the foundational storage layer of one of the world’s largest independent banks. This article explores the symbiotic relationship between Nubank’s mission to simplify banking and Datomic’s philosophy of data-driven simplicity. We analyze the technical challenges of scaling Datomic to serve over 114 million customers, focusing on innovations such as “implicit partitions” and the architectural shifts required to maintain a global-scale financial system. Furthermore, we examine how the “Datomic-as-a-Service” model within Nubank empowers thousands of developers to build resilient, high-performance microservices while maintaining the lowest cost-to-serve in the banking industry.
Simplicity as a Mission: The Nubank and Datomic Alignment
The acquisition of Cognitect (the creators of Clojure and Datomic) by Nubank was more than a corporate transaction; it was a meeting of shared values. Nubank was founded with the explicit goal of reducing the extreme complexity and high costs of the Brazilian banking sector. At the time, millions of Brazilians were unbanked, and interest rates for personal loans often exceeded 100% per year. Nubank sought to disrupt this by building a bank that was digital-first, customer-centric, and architecturally simple.
Datomic, with its focus on immutability, “database-as-a-value,” and the separation of reads from writes, provided the perfect technical backbone for this mission. Jordan highlights that the alignment on “simplicity” allowed the partnership to flourish. Today, Nubank serves 114.3 million users with an 83% activity rate, largely fueled by word-of-mouth referrals. The bank’s ability to scale rapidly while maintaining the lowest cost-to-serve globally is a direct consequence of an architecture that prioritizes developer productivity and system reliability through Datomic.
Architectural Innovation: Scaling the Immutable Store
Scaling a database to handle the needs of over 100 million customers requires rethinking traditional storage patterns. Within Nubank, Datomic is not just a database; it is a managed service provided to over 3,000 developers working across 1,000 microservices. This “Datomic-as-a-Service” (DaaS) model ensures that individual product teams do not need to worry about provisioning or maintaining their own database clusters.
A key innovation discussed by Jordan is the concept of implicit partitions. In standard Datomic, partitions are a way to group related data for better locality and performance. However, as the number of services and the volume of data grew at Nubank, manual partition management became a bottleneck. The Datomic team developed implicit partitions to automate this process, allowing the system to handle massive growth without manual intervention. This technical advancement is part of a broader effort to make Datomic “invisible” to the developer, allowing them to focus on business logic rather than storage mechanics.
The Power of “Database-as-a-Value”
The fundamental innovation of Datomic—treating the database as an immutable value—is what enables Nubank’s high-scale operations. In a traditional SQL database, “the” database is a moving target that changes with every update. In Datomic, a process can take a “snapshot” of the database at a specific point in time and perform complex queries against that static value. This eliminates many of the concurrency issues found in traditional systems and makes it trivial to implement features like “time-travel” auditing, which is critical for financial compliance.
Developer Success and the Future of Datomic
Jordan’s role at Nubank emphasizes that the success of a technology is as much about the people using it as it is about the code itself. The Datomic team at Nubank is committed to “Developer Success,” which involves building tools, documentation, and a culture that helps engineers leverage the database effectively. This includes the creation of a “Datomic Workshop” and active engagement with the Clojure community to ensure that Datomic continues to evolve as a world-class product.
The results of this focus are evident in Nubank’s operational efficiency. By providing a unified, simple, and powerful storage abstraction, Nubank has managed to grow by an average of 13 million customers per year since 2015 while keeping its infrastructure costs significantly lower than traditional banks. This demonstrates that functional programming and immutable databases are not just academic curiosities but are viable, high-performance solutions for the world’s most demanding financial environments.
Links:
[SpringIO2025] Taming Testing of AI apps by Alex Soto
Lecturer
Alex Soto is the Director of Developer Experience at Red Hat, a Java Champion, and an advocate for open-source software. With over 17 years in the tech industry, he specializes in Java development, software automation, and AI integration. Soto is a prolific author, having co-authored books like “Applied AI for Enterprise Java Developers” and “Quarkus Cookbook,” and he frequently speaks on testing, cloud-native applications, and AI challenges.
Abstract
This article examines the complexities of testing AI-integrated applications, addressing challenges like non-deterministic outputs, hallucinations, and bias. It discusses strategies for ensuring reliability, including synthetic data generation, evaluation metrics, and model-assisted testing. Drawing on practical examples, it highlights methodologies for validating both deterministic and probabilistic components, emphasizing the role of data scientists and robust testing frameworks in building trustworthy AI systems.
Challenges in Testing AI-Integrated Applications
Integrating large language models (LLMs) into applications introduces unique testing hurdles, primarily due to their non-deterministic nature. Responses from models like GPT or Grok vary even for identical inputs, complicating assertions. For instance, querying an image might yield “cat” one time and “kitten” another, rendering strict equality checks ineffective. This unpredictability stems from the probabilistic architecture of LLMs, which prioritize generating plausible answers over consistency.
Hallucinations exacerbate this: models may produce inconsistent outputs (e.g., “Alex is tall and short”), input-output mismatches (e.g., rude responses despite politeness prompts), or factually incorrect information (e.g., “the Earth is flat”). Such behaviors, akin to journalists offering opinions on unfamiliar topics, necessitate specialized testing to detect and mitigate risks.
Traditional testing paradigms falter here, as AI components act as “black boxes.” Developers must treat models as external services, focusing on integration points while acknowledging limited control over internal mechanics.
Strategies for Handling Non-Determinism and Hallucinations
To address non-determinism, employ evaluation metrics over binary pass/fail. Tools like Ragas compute faithfulness (alignment with context), answer relevance, and contextual precision. For example, in retrieval-augmented generation (RAG), Ragas assesses if responses accurately reflect retrieved documents, using scores from 0 to 1.
Synthetic data generation enhances testing realism. LLMs can create diverse datasets, simulating user inputs without privacy concerns. In a pet clinic demo, a model populates forms with realistic personas, verifying outputs against expectations.
For hallucinations, chain-of-thought prompting guides models toward reasoned responses, reducing errors. Assertions check for inconsistencies, such as ensuring polite outputs or factual accuracy via external verifiers.
Code for Ragas evaluation in Java:
import dev.langchain4j.rag.query.Query;
import io.ragas.RagasEvaluator;
RagasEvaluator evaluator = new RagasEvaluator();
Query query = new Query("What is Spring Boot?");
String response = model.generate(query);
double faithfulness = evaluator.evaluateFaithfulness(response, context);
assert faithfulness > 0.8;
This quantifies response quality, enabling threshold-based assertions.
Model-Assisted Testing and Integration Approaches
Leverage AI for test creation and execution. Tools like MCPlaywright use models to script browser interactions, generating tests dynamically. In the pet clinic example, prompts instruct models to navigate, fill forms with synthetic data, and verify tables, outputting pass/fail.
Involve data scientists early for model-specific insights, ensuring tests cover bias and drift. Test deterministic parts (e.g., API routing) separately from AI components, using mocks for isolation.
Be resource-conscious: unnecessary politeness in prompts wastes compute (e.g., “thank you” equates to energy for three water bottles). Focus on rude, direct interactions for efficiency.
Implications for Reliable AI Development
Testing AI apps demands a paradigm shift toward probabilistic validation, blending traditional unit tests with advanced evaluators. Synthetic data and model-assisted tools democratize realistic testing, but require strong testing fundamentals. As AI permeates critical systems, these strategies ensure fairness, safety, and robustness, mitigating risks like hallucinations in production.
Future directions include AI-driven test optimization, reducing human effort while enhancing coverage. Developers must balance innovation with rigor, treating AI as an enhancement rather than a core dependency.
Links:
[AWSReInvent2025] Scaling Customer Support, Compliance, and Productivity with Conversational AI at Coinbase
Lecturer
Joshua Smith is a Senior Solutions Architect at Amazon Web Services (AWS), specializing in financial services. He collaborates closely with major institutions to design scalable, secure cloud architectures.
Vara Maharivan serves as Director of Machine Learning and Artificial Intelligence at Coinbase, leading the company’s efforts to integrate advanced AI and machine learning capabilities across its cryptocurrency platform.
Abstract
This session examines how Coinbase, a leading cryptocurrency exchange, has deployed a unified generative AI platform built on Amazon Bedrock to transform three critical operational domains: customer support, regulatory compliance, and internal developer productivity. The presentation details the architectural approach, key AWS services leveraged, real-world performance metrics, and the strategic roadmap ahead. By combining retrieval-augmented generation (RAG), tool execution, and domain-specific agents, Coinbase has achieved substantial automation, cost efficiencies, and enhanced user experiences while maintaining rigorous security and compliance standards.
The Evolution of Generative AI in Financial Services
Joshua Smith opened the discussion by contextualizing the rapid maturation of generative AI within financial services. In 2023, early adoption centered on foundational concerns such as data trust and secure retrieval mechanisms. By 2024, the introduction of Amazon Bedrock enabled broader experimentation in areas like customer support, with focus shifting toward scalability, granular access controls, and integration with existing enterprise tools. Entering 2025, the landscape has progressed toward fully agentic, multi-agent systems capable of autonomously orchestrating complex workflows.
Smith emphasized that the primary challenge is no longer prototyping conversational interfaces but rather re-engineering entire business processes to deliver measurable impact on key performance indicators. This shift demands robust infrastructure, advanced security primitives, and operational frameworks tailored for agentic workloads.
AWS Services Enabling Production-Grade Agentic AI
Central to the discussion was Amazon Bedrock, a fully managed service providing access to leading foundation models through a unified API. Bedrock supports private model customization, guardrails for safety, cost-latency optimization, and, notably, Agent Core—a suite of capabilities designed to operationalize agents at scale.
Agent Core addresses critical production gaps: a serverless runtime supporting long-running multimodal agents (up to eight hours), checkpointing and recovery, identity management compatible with existing providers, secure token vaults, shared and private memory, tool discovery with fine-grained controls, and centralized observability combining logs, traces, and metrics. These components collectively mitigate risks highlighted in industry reports, such as escalating costs, unclear value, and insufficient security, which threaten the viability of agentic initiatives.
Coinbase’s Strategic Vision for AI Integration
Vara Maharivan outlined Coinbase’s mission to increase economic freedom through a trusted global cryptocurrency platform. The company rests on three pillars: building trust via top-tier security, enhancing accessibility through intuitive experiences, and scaling operations efficiently across more than 100 countries.
AI and machine learning have long underpinned fraud detection, risk assessment, personalization, and infrastructure scaling at Coinbase. Recent innovations include graph neural network-based risk scoring for blockchain addresses, ERC-20 scam token detection combining smart contract auditing with ML, and predictive scaling models to handle market volatility.
With the advent of large language models, Coinbase identified three high-impact generative AI domains: customer support automation, compliance process acceleration, and developer productivity enhancement.
Transforming Customer Support with Agentic Workflows
Crypto markets exhibit extreme volatility, driving unpredictable spikes in user inquiries that challenge traditional human-staffed support models. Coinbase addressed this through a unified generative AI platform granting fluid access to models and internal data via standardized interfaces.
The architecture features a virtual assistant handling routine interactions autonomously and an agent-assist tool empowering human representatives. The virtual assistant resolves straightforward cases end-to-end, while the assistive tool synthesizes real-time information from knowledge bases and tools, providing agents with contextual summaries, suggested responses, and multilingual capabilities.
Results demonstrate significant impact: approximately 65% of customer contacts are now automated, yielding nearly five million annualized employee-hour savings. Automated cases resolve in under ten minutes—contrasting sharply with up to forty minutes for human-handled escalations—dramatically improving customer satisfaction and operational efficiency.
Streamlining Compliance through AI-Augmented Investigations
Regulatory compliance in financial services demands rigorous processes such as KYC, KYB, and transaction monitoring. These workflows are labor-intensive, require exhaustive explainability, and must adapt to diverse jurisdictional requirements.
Coinbase augmented traditional ML-based risk detection models (deployed via Anyscale on AWS EKS) with generative AI. A compliance-assist tool aggregates data from internal systems and open-source intelligence, producing narrative summaries and risk signals for human reviewers.
At the core lies an autoresolution engine orchestrating holistic reviews. Upon a high-risk alert, the engine coordinates data synthesis, automated actions, human-in-the-loop feedback, and customer information requests. Final decisions—such as filing Suspicious Activity Reports—remain with human compliance officers, preserving accountability while accelerating throughput and consistency.
Boosting Developer Productivity across the SDLC
Developer efficiency emerged as another strategic priority. Coinbase provides multiple best-in-class coding assistants (e.g., Claude Code, Cursor) powered by Anthropic models via Bedrock, allowing engineers to select preferred tools.
A custom GitHub Action automates pull-request reviews: summarizing changes, generating natural-language comments, enforcing conventions, identifying testing gaps, and offering debugging guidance for CI failures. This shifts human review toward higher-value architectural concerns.
For quality assurance, an in-house UI testing tool translates natural-language test descriptions into autonomous browser actions across form factors, achieving parity with human accuracy, triple the bug-detection rate, and 86% cost reduction versus manual testing.
Quantifiable outcomes include nearly 40% of daily code being AI-generated or influenced (targeting 50%), 75,000 annual hours saved via automated PR reviews, and dramatically faster test introduction.
Future Directions and Platform Modernization
Coinbase aims to democratize agentic AI across the organization, enabling every employee to experiment and innovate. Ongoing efforts focus on modernizing existing tools and scaling enterprise-wide impact.
Agent Core features—secure deployment, robust identity management, advanced memory, and interoperability—are viewed as pivotal for the next phase of expansion.
Conclusion
The Coinbase case illustrates a mature approach to generative AI deployment: leveraging a unified platform on Amazon Bedrock to address volatility-driven operational challenges while upholding security and regulatory standards. By combining autonomous agents, human augmentation, and rigorous evaluation, the company has realized substantial automation, cost savings, and quality improvements across support, compliance, and engineering functions. As agentic systems evolve, such integrated architectures offer a blueprint for financial institutions seeking transformative efficiency without compromising trust.
Links:
[MiamiJUG] Bridging the Gap: A Java Developer’s Guide to the Go Ecosystem
Lecturer
Vladimir Vivien is a veteran software engineer with over 20 years of experience in the technology industry. A specialist in distributed systems and cloud-native architecture, Vladimir spent the first decade of his career as a dedicated Java developer before transitioning to the Go programming language roughly twelve years ago. He is the author of the authoritative text Learning Go Programming and the creator of the LinkedIn Learning course Programming with Go Modules. Vladimir is a passionate advocate for well-architected solutions and currently focuses on building high-performance systems that leverage Go’s unique concurrency primitives.
Abstract
As the backbone of cloud-native infrastructure, the Go programming language (Golang) has become an essential tool for modern software engineering. This article provides a comparative analysis of Go and Java, designed specifically for practitioners familiar with the Java Virtual Machine (JVM) ecosystem. While both languages share a commitment to static typing and garbage collection, they diverge significantly in their approaches to concurrency, deployment, and error handling. By exploring Go’s syntax, its “share by communicating” philosophy via channels, and its deterministic build system, this study highlights how Go simplifies common programming tasks while maintaining the performance required for large-scale systems like Kubernetes and Docker. The analysis concludes by examining Go’s role in the industry and its strategic advantages for distributed architectures.
The Origins and Industry Adoption of Go
Go was developed at Google to solve large-scale software engineering challenges. It was designed not merely as a language, but as a comprehensive suite of tools to address issues like packaging, supply chain security, and build-time performance. Since its public release in 2009, Go has consistently ranked among the most loved languages by developers.
Go’s dominance is particularly evident in the cloud-native and DevOps sectors. Critical infrastructure tools such as Kubernetes, Docker, Terraform, and Prometheus are all written in Go. This is not coincidental; Go’s ability to compile into a single, static binary with fast startup times and low memory overhead makes it ideal for containerized environments. Vladimir notes that while Java offers “Write Once, Run Anywhere” via the JVM, Go provides “Write Once, Compile Anywhere,” targeting specific architectures with a highly optimized toolchain.
Comparative Architecture: Go vs. Java
For the Java developer, Go introduces several paradigm shifts in how code is structured and executed:
Static Typing and Inference
Both languages utilize strict static type systems. However, Go supports implicit typing through the := short variable declaration operator, allowing the compiler to infer the type based on the assigned value. This provides the brevity of a dynamic language while maintaining the safety of static checks at compile time.
Garbage Collection
Go and Java are both garbage-collected. However, whereas Java provides developers with numerous “knobs” and parameters to tune the JVM’s garbage collector, Go takes a minimalist approach. The Go runtime is designed to deliver sub-millisecond GC pauses with almost no manual configuration, relying on compiler optimizations and escape analysis to manage memory efficiently.
Concurrency: Go-routines and Channels
The most significant departure from Java’s threading model is Go’s approach to concurrency. Instead of heavy OS-level threads, Go uses “go-routines”—lightweight threads managed by the Go runtime that cost only a few kilobytes of memory.
Go’s philosophy of concurrency is summarized as: “Do not communicate by sharing memory; instead, share memory by communicating.” This is achieved through Channels, conduits that allow go-routines to pass data safely without the need for traditional locks or race condition worries.
Example of a basic worker pattern in Go:
func worker(id int, jobs <-chan int, results chan<- int) {
for j := range jobs {
results <- j * 2
}
}
func main() {
jobs := make(chan int, 100)
results := make(chan int, 100)
for w := 1; w <= 3; w++ {
go worker(w, jobs, results) // Launch 3 lightweight go-routines
}
for j := 1; j <= 5; j++ {
jobs <- j
}
close(jobs)
// Results are popped out as they are processed
}
Explicit Error Handling and Resource Management
Unlike Java, which relies on a hierarchy of Exceptions that bubble up the call stack, Go requires explicit error handling. Functions in Go can return multiple values, and by convention, the last value is often an error type.
Vladimir explains that this “check everything” approach prevents silent failures and forces developers to consider failure states as part of the primary logic flow. Additionally, Go replaces Java’s try-with-resources or finally blocks with the defer keyword, which schedules a function call (like closing a file or network connection) to run immediately before the surrounding function returns.
Conclusion: Where Go Shines
Go’s design choices prioritize simplicity, readability, and performance. It excels in building CLI tools, distributed systems, and high-performance APIs capable of handling thousands of concurrent connections out of the box. For the Java developer, Go offers a streamlined alternative that reduces the complexity of modern cloud-native development without sacrificing the robustness required for enterprise-scale engineering.
Links:
[AWSReInforce2025] Securing AWS networks: Observability meets defense-in-depth (NIS306)
Lecturer
AWS security specialists architect network protection strategies that combine stateful inspection, stateless filtering, and continuous verification across multi-account environments. Their expertise encompasses VPC design patterns, traffic visibility frameworks, and policy orchestration at planetary scale.
Abstract
The session establishes a comprehensive network security framework that integrates layered controls—Security Groups, NACLs, Network Firewall, DNS Firewall—with observability tools including VPC Flow Logs, Reachability Analyzer, and Network Access Analyzer. Through architectural patterns and operational workflows, it demonstrates how organizations achieve defense-in-depth while maintaining visibility across complex, multi-VPC topologies.
Evolving Threat Landscape and Network Attack Surface
Modern networks face persistent, multi-vector threats. Ransomware campaigns exploit weak egress controls to reach command-and-control servers. DDoS attacks target application availability through volumetric or protocol exhaustion. Supply chain compromises leverage DNS tunneling for data exfiltration.
The network remains the primary attack surface because:
- All traffic traverses it
- Misconfigurations compound rapidly across accounts
- Traditional perimeter defenses fail in cloud-native architectures
Defense-in-Depth Control Layers
AWS implements security through progressive filtering:
Internet → Route 53 Resolver → DNS Firewall
↓
Gateway Load Balancer → Network Firewall
↓
Security Groups → NACLs → Application
Each layer operates with distinct scope:
– DNS Firewall: Blocks malicious domains before connection establishment
– Network Firewall: Performs stateful inspection with intrusion prevention
– Security Groups: Enforce instance-level allow rules
– NACLs: Provide stateless subnet boundaries
Observability Integration Architecture
Visibility requires purpose-built telemetry:
sources:
- vpc_flow_logs:
sampling: 100%
format: parquet
- firewall_logs:
destination: s3://central-logs
- dns_query_logs:
enable: true
Centralized collection in a dedicated log archive account enables cross-account analysis. Athena queries identify anomalous patterns:
SELECT source_ip, destination_domain, count(*)
FROM dns_logs
WHERE resolution = 'NXDOMAIN'
GROUP BY 1, 2 HAVING count(*) > 1000
Reachability Analyzer for Connectivity Validation
The tool models network paths programmatically:
aws networkmanager create-reachability-analysis \
--source-type VPC \
--source-id vpc-12345678 \
--destination-type InternetGateway
Results reveal unintended egress routes, overlapping CIDR blocks, or missing firewall traversal. Integration with CI/CD pipelines prevents insecure infrastructure deployment.
Network Access Analyzer for Policy Verification
This service evaluates effective permissions:
{
"scope": "VPC",
"findings": [
{
"resource": "subnet-12345678",
"issue": "Internet accessible",
"path": "NACL allow 0.0.0.0/0"
}
]
}
Findings integrate with Security Hub for automated remediation via Lambda—revoking public access, enforcing VPC endpoints.
Multi-Account Governance Patterns
Reference architecture implements centralized control:
Management Account → Firewall Manager Policies
→ Security Account (Logging + Analysis)
→ Workload Accounts (VPCs)
Firewall Manager enforces baseline Network Firewall rulesets across 1000+ accounts. SCPs prevent deviation from approved configurations.
Operational Workflows and Incident Response
Security teams operationalize the framework through:
- Daily Monitoring: CloudWatch dashboards track rejected packets
- Threat Hunting: Athena federated queries across flow logs
- Incident Playbooks: EventBridge triggers isolation via Security Group updates
- Compliance Reporting: Automated evidence collection for audits
Conclusion: Integrated Security Fabric
The convergence of layered controls and continuous observability creates a resilient network security posture. Organizations eliminate blind spots through centralized telemetry, proactive reachability validation, and policy enforcement at scale. This integrated approach transforms network security from reactive defense into a strategic enabler of cloud adoption.
Links:
[DevoxxBE2025] From the Comfort of AWS to the Unknown of GCP and Back
Lecturer
Natalie Godec is a Senior Cloud Architect at Zenops, specializing in multi-cloud migrations and platform engineering. Endy Kasanardjo is a Cloud Architect at Zenops, with focus on Kubernetes and data systems for scalable infrastructures.
Abstract
This review details a platform migration from AWS to GCP, underscoring unanticipated issues in containerized setups. It elucidates equivalency mappings, replication hurdles, and rollback tactics, within business realignments. Through phased execution and troubleshooting, it dissects tooling variances and reliability impacts. Effects on operational continuity and team preparedness are analyzed, yielding guidance for robust cloud shifts.
Strategic Motivators and Planning Phases
Shifts often arise from alliances, favoring providers. The system—microservices with Kubernetes, GitLab, Flux, Prometheus, Terraform, Kafka, PostgreSQL—appeared transferable. Assumptions ignored nuances.
Context: AWS maturity versus GCP features, promising synergies. Planning mapped: EKS to GKE, S3 to GCS. Dual operations tested, DNS for switchover.
Challenges: GCP defaults required tweaks. Implications: audits essential for timelines.
Implementation and Technical Obstacles
Phases: Terraform replication, redeployment, synchronization. GKE setup paralleled EKS, but scaling failed from CIDR fragmentation—pod ranges sliced for nodes, depleting allocations.
Data used DMS for PostgreSQL, MirrorMaker2 for Kafka, but bucket races failed. Secrets mismatched.
Cutover: DNS changes, but failures prompted reversions. Method: blue-green for safety.
Analysis: monitoring bridged providers. Implications: hybrids during transitions maintain service.
Reversion Tactics and Refinements
Reversions critical: first for uploads, second for scaling. Fixes: CIDR expansions, secret fixes.
Method: dashboards alerted anomalies. Iterations built assurance, succeeding on GCP.
Consequences: reversions safeguarded uptime, but stressed testing needs.
Insights for Multi-Cloud Resilience
Migrations reveal subtle locks. Insights: empirical validation, data priority, reversibility prep.
Implications: abstractions cut costs. Team training speeds adaptations.
In overview, the shift affirmed robustness, shaping agile strategies.
Links:
- Lecture video: https://www.youtube.com/watch?v=70AuY_mShrI
- Natalie Godec on LinkedIn: https://www.linkedin.com/in/natalie-godec/
- Natalie Godec on Twitter/X: https://twitter.com/natalie_godec
- Endy Kasanardjo on LinkedIn: https://www.linkedin.com/in/endy-kasanardjo-8b8a0b1b/
- Zenops website: https://zenops.io/
[GoogleIO2025] Demis Hassabis on the frontiers of AI
Keynote Speakers
Demis Hassabis holds the position of Co-Founder and Chief Executive Officer at Google DeepMind, directing pioneering research in artificial general intelligence, with breakthroughs in areas like game mastery and biological modeling. A University College London PhD in cognitive neuroscience, he has been knighted for scientific services.
Alex Kantrowitz acts as the founder and host of Big Technology Podcast, exploring technological impacts through interviews with industry leaders. His journalistic career includes contributions to CNBC, focusing on innovation’s societal ramifications.
Abstract
This analytical discourse scrutinizes a dialogue on AI’s vanguard, featuring perspectives on model advancements, scaling debates, and societal transformations. It unpacks concepts of algorithmic versus computational progress, ethical deployments, and speculative futures like artificial general intelligence. Through contextualizing within rapid technological strides, the narrative assesses methodologies for responsible innovation and implications for global economies, education, and existential paradigms.
Progress Trajectories and Scaling Debates
Demis Hassabis and Sergey Brin, moderated by Alex Kantrowitz, initiate by forecasting AI model enhancements, positing substantial untapped potential via existing techniques and nascent breakthroughs. Hassabis advocates balancing exploitation of known methods—like data and compute scaling—with exploratory inventions, suggesting one or two pivotal discoveries may unlock AGI.
Brin concurs, citing historical precedents where algorithmic leaps outpace hardware gains, even amid Moore’s Law. He references N-body simulations, implying similar dynamics in AI, where ingenuity amplifies computational efficiency.
Contextually, this counters narratives of plateauing gains, attributing optimism to demonstrated accelerations, like those in Gemini iterations. Implications include sustained investment in dual tracks, fostering hybrid ecosystems where scale complements creativity, potentially accelerating societal benefits in domains like healthcare.
Ethical Deployments and Societal Ramifications
The conversation pivots to responsible AI, with Hassabis emphasizing Google’s safety protocols, including red teaming and watermarking. He delineates challenges in multimodal systems, where verifying audio or video veracity demands novel safeguards.
Brin reflects on AI’s transformative potential, likening it to electricity’s ubiquity, predicting pervasive integration reshaping industries. Hassabis concurs, envisioning AI as intellectual amplifiers, democratizing expertise in fields like drug discovery.
Methodologically, this involves iterative safety integrations from inception, implying proactive governance to mitigate risks like misinformation. Contexts encompass regulatory landscapes, where balanced policies could harness AI for global challenges, such as climate modeling.
Implications span equitable access, urging mitigation of biases to prevent exacerbating inequalities, while fostering interdisciplinary collaborations for holistic advancements.
Speculative Futures and Philosophical Underpinnings
Speculation on AGI timelines places it pre- or post-2030, with Hassabis leaning post, underscoring uncertainties. Discussions on simulation hypotheses probe reality’s computational nature, with Brin invoking recursive arguments against anthropocentric views.
Hassabis posits an information-theoretic universe, hinting at deeper inquiries into AI’s modeling capabilities. Implications extend to philosophical reevaluations, where AI blurs human-machine boundaries, potentially redefining cognition and existence.
Overall, the dialogue contextualizes AI’s trajectory within human ingenuity, implying transformative yet navigable futures through ethical stewardship.
Links:
[AWSReInvent2025] Basketball’s AI Revolution: How AWS and the NBA Are Changing the Game
Lecturer
Chris Benyarko is Executive Vice President of Direct-to-Consumer at the NBA, overseeing fan engagement and digital strategies. Andy Oh serves as Principal of Live Sports Events at Prime Video, leading NBA broadcasting partnerships. Kristen Schaff is Global Director of Sports Partnerships at AWS, managing collaborations across major leagues. Relevant links include Chris Benyarko’s LinkedIn profile (https://www.linkedin.com/in/chris-benyarko-/) and Kristen Schaff’s LinkedIn profile (https://www.linkedin.com/in/kristen-schaff/).
Abstract
This article investigates the NBA’s digital transformation via AWS, focusing on AI-driven analytics, fan personalization, and broadcasting innovations. It analyzes partnerships enhancing game strategies, viewer experiences, and global engagement, with implications for sports technology scalability.
The NBA-AWS Partnership: Shared Vision and Technological Foundations
The NBA’s strategic alliance with AWS, formally unveiled on October 1st, is rooted in a mutual commitment to innovation and an unwavering focus on fan experiences. Chris Benyarko emphasizes that this partnership transcends mere technology provision, positioning AWS as a true collaborator in advancing the league’s goals. At its foundation lies a shared philosophy: while the NBA prioritizes fan and future fan obsession, AWS brings its renowned customer-centric approach, creating a synergy that amplifies their joint efforts. This alignment enables the league to harness AWS’s robust infrastructure for seamless integration across various operations, ultimately accelerating the pace of technological advancements.
In the broader context of basketball’s ongoing evolution, the need for sophisticated, data-driven solutions has never been more pressing. AWS offers a scalable cloud platform that excels in handling complex analytics, artificial intelligence, and machine learning tasks, converting vast amounts of raw data into meaningful insights that inform decision-making at every level. Kristen Schaff highlights what drew AWS to the NBA, pointing out the league’s dynamic, fast-paced nature and its abundance of data as ideal attributes that align perfectly with AWS’s technological strengths. From player performance tracking to predictive modeling, this collaboration leverages AWS’s tools to address the unique demands of professional sports.
The methodology underpinning this partnership involves a comprehensive migration of workflows to AWS services, ensuring low-latency streaming and personalized content delivery that reaches audiences worldwide. By combining the NBA’s deep domain knowledge with AWS’s technical prowess, the alliance not only enhances current offerings but also paves the way for future innovations that could redefine the sport.
AI and Analytics Transforming Gameplay and Strategy
Artificial intelligence is at the forefront of reshaping basketball analytics, influencing everything from individual player development to collective team strategies during games. Chris Benyarko delves into the capabilities of Second Spectrum’s optical tracking system, which deploys 29 cameras in each arena to capture an astonishing 100 million data points per night. These metrics encompass detailed aspects such as player speed, defensive positioning, and shot quality, providing coaches and analysts with granular information that was previously unattainable.
AWS plays a pivotal role in this transformation by powering machine learning models that forecast game outcomes and simulate various scenarios, thereby assisting coaches in refining their tactics. The implications are significant, as teams can now gain substantial competitive advantages through data-informed decisions, while fans benefit from enriched content on platforms like NBA League Pass, including automated highlight reels that capture the most thrilling moments. Andy Oh complements this by describing how Prime Video integrates AWS for real-time statistical overlays, which add layers of depth to the viewing experience and foster greater immersion.
Nevertheless, challenges such as data latency persist, and the partnership addresses these through continuous infrastructure optimizations, ensuring that the flow of information remains timely and reliable.
Enhancing Fan Engagement Through Personalization
Personalization has emerged as a key driver in elevating fan engagement, utilizing AI to deliver content that resonates on an individual level. Chris Benyarko explains the progression of NBA League Pass, which now employs AI to generate highlights in multiple languages, offer alternate viewing streams focused on specific players, and provide predictive elements like real-time win probabilities. These features not only cater to diverse global audiences but also deepen the connection between fans and the game.
AWS’s extensive global network facilitates this by guaranteeing low-latency delivery to over 200 countries, making high-quality experiences accessible regardless of location. Kristen Schaff underscores the importance of data privacy within these personalization efforts, ensuring that the NBA’s fan-first principles are upheld through secure, unified data management practices.
An analysis of this approach reveals its potential to shift traditional passive spectatorship toward more interactive and tailored interactions, which in turn boosts viewer retention and opens new avenues for monetization through precisely targeted advertising.
Broadcasting Innovations and Latency Challenges
Prime Video’s integration of NBA content exemplifies how AWS enables groundbreaking broadcasting innovations. Andy Oh outlines the process of capturing feeds directly from arenas and minimizing transmission hops to achieve near-real-time delivery, a critical factor especially for integrations involving live betting.
Among the notable advancements is AI-generated commentary available in various languages, powered by AWS Bedrock for natural and accurate translations. The broader implications extend to democratizing access to premium content, thereby expanding the NBA’s global footprint and attracting new demographics. However, the persistent challenge of avoiding spoilers drives an ongoing emphasis on latency reduction, with AWS tools providing the means for continuous monitoring and swift adjustments to maintain optimal performance.
Implications for Sports and Broader Industries
The NBA-AWS partnership offers valuable insights that transcend the realm of sports, demonstrating the power of real-time data platforms, personalized content delivery, and AI in production environments. Chris Benyarko envisions extending these technologies to non-professional leagues, potentially increasing participation by making advanced analytics more widely available.
Looking ahead, AI could further innovate by predicting injuries or optimizing training regimens, fundamentally altering athletic preparation and performance. These developments not only enhance the sport but also provide scalable models applicable to other industries seeking to leverage data for competitive advantage.
Conclusion
The synergy between AWS and the NBA vividly illustrates the transformative potential of AI in sports. By enhancing analytics, personalization, and broadcasting through advanced cloud technologies, this collaboration redefines fan engagement and sets a precedent for innovation across various sectors.
Links:
- https://www.youtube.com/watch?v=pZczwGVzWxo
- https://www.linkedin.com/in/chris-benyarko-/
- https://www.linkedin.com/in/kristen-schaff/
[AWSReInventPartnerSessions2024] Usage
spec = “Sort a list of numbers”
code = generate_code(spec)
tests = [([3, 1, 2], [1, 2, 3]), ([5, 4], [4, 5])]
if test_code(code, tests):
print(“Code passes tests”)
“`
This exemplifies the iterative process of generation and validation central to the platform.
Analytical Implications for Efficiency and Innovation
The deployment of GenWizard reveals profound implications for operational efficiency. By automating repetitive tasks, it allows teams to focus on high-value activities, reducing project timelines by up to seventy percent in some cases. This efficiency stems from the platform’s ability to handle complex correlations and predictions, as seen in incident management where noise reduction leads to faster resolutions.
Innovation is fostered through enhanced decision-making. The system’s knowledge base, enriched with historical data and AI insights, supports proactive strategies like predictive maintenance and application rationalization. For instance, analyzing application portfolios identifies redundancies, enabling cost savings and streamlined operations.
Collaboration with technology partners like AWS amplifies these benefits. Amazon Q’s integration ensures seamless natural language interactions, democratizing access to advanced tools and promoting a culture of continuous improvement.
Consequences for Enterprise Adoption and Future Directions
Enterprise adoption of such platforms mitigates risks associated with legacy systems, facilitating smoother migrations and modernizations. However, challenges include ensuring data privacy and model accuracy, addressed through robust governance frameworks.
Future directions involve expanding agentic capabilities to encompass more lifecycle stages, potentially incorporating multimodal AI for broader applications. This could revolutionize industries by enabling autonomous operations, where systems self-optimize based on real-time data.
In conclusion, the fusion of generative AI with service delivery platforms like GenWizard, powered by AWS, represents a paradigm shift toward intelligent, efficient technology management, promising sustained competitive advantages.
Links:
[KotlinConf2025] Blueprints for Scale: What AWS Learned Building a Massive Multiplatform Project (2nd version)
In a talk on building large-scale, multiplatform projects, Ian Botsford and Matis Lazdins of Amazon Web Services (AWS) shared their experiences creating the AWS SDK for Kotlin. This project is colossal, spanning over 300 services and targeting eight different platforms, with its code distributed across four repositories and nearly 500 Gradle modules. The talk provided a blueprint for managing a codebase with over 8.6 million lines of code, 98% of which is auto-generated. The key to their success, they claimed, was a set of five core principles that kept their maintainers sane and productive.
A Principled Approach to Development
Botsford and Lazdins detailed five tenets for managing a project of this scale: owning your dependencies, structuring the project for growth, designing for Kotlin Multiplatform (KMP) from the beginning, maintaining backward compatibility, and optimizing the maintainer experience. They provided a practical example of owning dependencies by discussing their choice of HTTP clients. Instead of exposing third-party library types directly, which could lead to inconsistent configurations and vulnerability to unexpected API changes, they created a common, abstract interface to maintain consistency and shield users from underlying implementation details.
Automating for Maintainer Sanity
A significant part of their strategy focused on the maintainer experience. Lazdins explained the importance of automating repetitive and mundane tasks to free up time for more complex work. They developed broad checks to catch issues before they are merged, which helps prevent regressions and enforce project standards. The speakers stressed that these checks should be highly informative but also overridable, giving developers autonomy while providing valuable feedback. This focus on a positive maintainer experience is crucial for the health of any large open-source project and is a key factor in the daily releases that happen sometimes multiple times a day.