OffNet Newsroom

Archive snapshot

Wednesday, September 16, 2026

Daily signal on databases, AI, and the tech that matters.

48 new today 51 stories 8 sections 16 for the DBA desk

Database Technology 8

roundup ↗

Percona has released version 8.4.11-11, which includes targeted patches designed to improve overall performance. This update builds upon the broader performance progression observed in the 8.4 series released earlier in 2026. The release focuses on specific optimizations to enhance efficiency for MySQL workloads.

  • Version 8.4.11-11 introduces patches for significant performance gains.
  • Optimizations build on the 8.4 series progression established in 2026.
  • Review prior 8.4 performance analysis for full context on these changes.
  • Consider testing this patch version to validate efficiency improvements.
CHECKLISTAction Plan for 8.4.11-11Review prior 8.4 performance analysisTest patch to validate improvementsNote optimizations for MySQL workloads

PostgreSQL 19 introduces two new contrib modules to stabilize query execution plans when data growth causes the planner to select suboptimal paths. pg_plan_advice allows users to capture a specific plan as a string and enforce it for future executions. pg_stash_advice automates this by storing these plan strings keyed by query ID and applying them automatically.

  • Stabilizes queries that degrade after ANALYZE due to data growth without code changes
  • pg_plan_advice enables manual capture and enforcement of specific execution plans
  • pg_stash_advice automates plan enforcement using query ID keys for seamless operation
  • Both modules are part of the contrib extension and available in PostgreSQL 19 Beta 3
TRADE-OFFPlan Control MethodsManual ControlCapture plan as stringEnforce specific plan manuallyAutomated ControlStore plans by query IDApply plans automaticallyvs

On PostgreSQL 17, a prepared statement can execute quickly for five runs before the query planner changes its strategy, causing a significant performance drop on the sixth execution. This behavior is invisible to single-run diagnostics like a standard EXPLAIN ANALYZE, requiring repeated executions to detect the plan shift. The issue stems from the internal plan cache mechanism and affects various drivers, not just psql.

  • Single EXPLAIN ANALYZE runs mask plan instability that emerges after repeated executions.
  • Prepared statements may trigger a plan cache update that degrades performance on run six.
  • Use multiple repetitions in benchmarks to detect intermittent plan changes.
  • This behavior is specific to PostgreSQL 17 and the plan cache mechanism.
  • A one-line fix exists to mitigate the issue in affected driver configurations.

Agoda migrated its 1.5 TB hotel Price Cache from a complex 72-shard SQL Server architecture to two DragonflyDB clusters. The team executed the migration using staged dual reads, parity validation, and gradual traffic shifting to ensure data consistency. Post-migration, the organization observed an eightfold reduction in P99 read latency while maintaining high availability.

  • Migrating from 72 SQL Server shards to DragonflyDB simplified infrastructure for a 1.5 TB dataset.
  • Staged dual reads and parity validation ensured data integrity during the traffic shift.
  • P99 read latency improved approximately eightfold after the migration.
  • Two DragonflyDB clusters provided the necessary high availability for the price cache.
THE SHIFTAgoda Latency Improvement1.5TBSQL SERVER CACHE99P99 LATENCYEightfold reduction achieved

An InfoQ article demonstrates how PostgreSQL can function as the sole durable state store for workflows, removing the dependency on external orchestration tools. The approach leverages SKIP LOCKED for concurrent processing, primary-key checkpoints for idempotency, and leases for crash recovery. It also shows how to persist long-running states like sleeps and human approvals directly in the database.

  • SKIP LOCKED enables safe concurrent work processing without complex locking logic.
  • Primary-key checkpoints enforce idempotency, preventing duplicate execution on restart.
  • Leases provide crash recovery mechanisms to handle node failures gracefully.
  • Workflow pauses and human approvals can be stored as database rows for durability.

PostgreSQL 19's SQL/PGQ feature is facing criticism due to unresolved bugs that could hinder production readiness. The project team acknowledges these issues, suggesting the current state fails a strict shipping viability test. Meanwhile, the introduction of concurrent REPACK offers a practical alternative for maintenance, potentially reducing the need for disruptive midnight operations for database administrators.

  • SQL/PGQ in PG19 has unresolved bugs; expect caution before adopting for graph workloads.
  • Concurrent REPACK is available, allowing index rebuilds without long-term locking.
  • DBAs can reduce overnight maintenance windows using the new REPACK capabilities.
  • Monitor upstream for bug fixes on SQL/PGQ before planning graph-based migrations.
AWS Database Blog awsdatabase

Aurora PostgreSQL Part 1: Diagnosing Row Lock Contention

AWS Database Blog Part 1 explains how PostgreSQL row locking mechanics can degrade throughput during traffic spikes despite healthy CPU and I/O metrics. The guide details methods to monitor lock contention using system views, the pgrowlocks extension, and the log_lock_waits parameter. This foundational knowledge supports troubleshooting efforts in both Amazon Aurora PostgreSQL and Amazon RDS for PostgreSQL environments.

  • Row lock contention can bottleneck throughput even when CPU and I/O remain healthy.
  • Use system views and pgrowlocks extension to identify specific locked rows.
  • Enable log_lock_waits parameter to capture detailed lock wait events.
  • Techniques apply to both Aurora PostgreSQL and standard RDS for PostgreSQL.

Fleet impact: For Aurora PostgreSQL and RDS for PostgreSQL fleets, this blog provides the diagnostic baseline needed to distinguish between resource saturation and locking issues during peak loads. Ensure log_lock_waits is tuned appropriately in your parameter groups to capture sufficient context for future contention analysis.

LLMs 8

roundup ↗
AWS What's New awsdatabase

Qwen3.6-35B and Wan2.1 models added to SageMaker JumpStart

Amazon SageMaker JumpStart now hosts NVIDIA-optimized Qwen3.6-35B-A3B-NVFP4 and Alibaba's Wan2.1-T2V-1.3B-Diffusers models. The Qwen variant is a Mixture-of-Experts architecture with 35B total parameters but only 3B active per token, featuring NVFP4 quantization for agentic coding and long-context tasks. Wan2.1 provides lightweight text-to-video generation capabilities directly to AWS customers.

  • Qwen3.6 uses MoE with 3B active parameters per token, reducing inference compute vs full 35B dense models.
  • NVFP4 quantization on Qwen3.6 optimizes memory and speed for agentic coding and multimodal reasoning.
  • Wan2.1 offers a 1.3B parameter diffusion model for efficient text-to-video generation workflows.
  • Both models are immediately deployable via SageMaker JumpStart for scalable AI solution building.
TRADE-OFFQwen3.6 vs Dense ModelsQwen3.6 MoE35B total parameters3B active per tokenNVFP4 quantizationTraditional Dense35B active per tokenHigher compute costFull memory usagevs

Typesafe has launched System One Models and a tool named Jev to help engineers build reliable AI agents. The release focuses on providing deterministic control planes and debugging capabilities for LLM-based workflows. This approach aims to bring enterprise-grade stability to complex agent architectures.

  • System One Models offers a structured framework for managing AI agent lifecycles.
  • Jev provides specialized debugging and observability for agent traces.
  • Targets the reliability gap in non-deterministic LLM workflows.
  • Enables deterministic control planes for production-grade AI systems.

Mistral AI's Ministral-3-3B and 8B instruct models are now available on Amazon SageMaker JumpStart. The 3B variant is optimized for ultra-lightweight edge deployment, combining a 3.4B language model with a 0.4B vision encoder. It requires only 8GB of VRAM in FP8 format while supporting a 256K-token context window.

  • Ministral-3-3B fits in 8GB VRAM (FP8) for resource-constrained edge environments.
  • Supports 256K-token context windows despite its compact model size.
  • Integrates a 0.4B vision encoder for multimodal understanding capabilities.
  • Expanded SageMaker JumpStart portfolio adds purpose-built foundation models.
BY THE NUMBERS256K Context in 8GB256KToken context window sizein 8GB VRAM with Ministral-3-3B

Amazon SageMaker JumpStart now hosts Google DeepMind's Gemma-4-31B-it-assistant and NVIDIA's Gemma-4-31B-IT-NVFP4 models. These variants of the 31B dense architecture support multimodal reasoning, coding, and agentic workflows with a 256K context window. The availability includes both a standard assistant-tuned version and an NVIDIA-optimized quantized option for scalable deployment.

  • SageMaker JumpStart adds Gemma-4-31B in full-precision and NVIDIA NVFP4 quantized forms.
  • Models support multimodal inputs including text, images, and video frame sequences.
  • Optimized for agentic workflows and coding tasks with a 256K context window.
  • Provides enterprise-ready deployment paths for high-performance AI on AWS.
  • NVIDIA variant offers quantization benefits for efficient inference scaling.
TRADE-OFFGemma-4-31B Deployment OptionsStandard VariantFull precision performanceAssistant tuned modelGeneral enterprise useNVIDIA NVFP4 VariantQuantized for efficiencyScalable inference speedOptimized for AWSvs

This paper introduces inference networks, a graph-based framework where nodes represent distinct LLMs and edges define conditional activation paths. The approach addresses the lack of principled strategies for combining expert models in ensemble or series configurations. By dynamically routing queries based on complexity, the system aims to balance inference costs with performance. It provides a structured method to leverage multiple models rather than relying on a single large model for all tasks.

  • Uses graph structures to map conditional activation paths between different LLMs.
  • Enables dynamic routing of simple queries to cheaper models and complex ones to powerful ones.
  • Addresses the gap in systematic strategies for combining expert models in synergy.
  • Offers a framework to optimize the trade-off between inference cost and model performance.
HOW IT WORKSDynamic Model Routing Pipeline1Analyze Query Complexity2Select Optimal Model Path3Activate Conditional Nodes4Execute Inference5Return Result
Hacker News (100+ points) general

Google launches Gemini 3.8 Live and Extended Thinking models

Google has released Gemini 3.8 Live alongside a new Extended Thinking variant, aiming to improve real-time interaction capabilities and complex reasoning. The update focuses on lowering latency for live use cases while providing deeper analytical steps for difficult problems. This release represents a significant step in Google's current model iteration strategy for generative AI applications.

  • Gemini 3.8 Live targets reduced latency for real-time conversational agents
  • Extended Thinking mode offers deeper reasoning chains for complex tasks
  • Release includes both standard and extended variants for different workload needs

ZGCM-1 is a fully open 7B dense foundation model trained from scratch to handle math and agentic search tasks efficiently. It addresses parametric capacity limits by coupling deliberate internal thinking with active external tool use. The training recipe features an end-to-end high-efficiency design, including interleaved gated sliding-window and full attention mechanisms, and stable FP8 Muon optimization.

  • Compact models can exceed parametric limits via internal reasoning + external tool use.
  • Architecture uses interleaved gated sliding-window and full attention for 256K context.
  • Training employs stable FP8 Muon optimizer for system and algorithmic efficiency.
  • Progressive curriculum scales context from 16K to 256K during mid-training.
  • Interaction traces are reformulated into Markov Decision Processes for better learning.
THE SHIFTContext Scaling Strategy16KSTARTING CONTEXT256KFINAL CONTEXTProgressive curriculum during training

TimeThink addresses the inability of current timeseries multimodal LLMs to handle out-of-distribution compositional questions. The framework uses synthetic data to elicit explicit reasoning capabilities, moving beyond the implicit answers that fail in high-stakes domains. It specifically targets the gap where reinforcement learning models struggle with dynamic temporal patterns and complex queries.

  • Current TS-MLLMs lack explicit reasoning for high-stakes applications like healthcare.
  • TimeThink provides a synthetic framework to elicit compositional timeseries reasoning.
  • Addresses failures in out-of-distribution queries that plague RL-based models.
  • Enables better handling of dynamic temporal patterns through structured primitives.
HOW IT WORKSTimeThink Reasoning Pipeline1Identify dynamic temporal patterns2Decompose complex queries3Apply structured primitives4Generate explicit reasoning5Validate out-of-distribution results

AI / ML 4

roundup ↗

Amazon SageMaker AI now allows users to submit a prioritized list of instance types for training and processing jobs instead of specifying a single option. This feature automates capacity selection, enabling the service to pick the first available instance from the provided list. It eliminates the need for complex custom retry logic or concurrent job submissions during periods of high GPU demand.

  • Submit multiple instance types in a prioritized list to let SageMaker select available capacity automatically.
  • Reduces job submission latency during peak demand without requiring custom orchestration scripts.
  • Simplifies workflows for workloads that function equivalently across different instance sizes or types.
  • Removes the operational overhead of managing concurrent jobs or complex retry mechanisms.
CHECKLISTSimplify GPU Instance SelectionSubmit prioritized list of instance typesLet SageMaker auto-select available capacityReduce job latency during peak demandEliminate custom orchestration scripts and retries

Amazon SageMaker JumpStart now hosts three new foundation models: IBM's granite-speech-4.1-2b, Kakao's kanana-2-30b-a3b-instruct, and OpenFold3. These additions expand AWS's AI portfolio with specialized capabilities for multilingual speech recognition, bilingual agentic workflows, and biomolecular structure prediction. The models are ready for deployment on AWS infrastructure to address specific enterprise AI challenges.

  • IBM granite-speech-4.1-2b handles multilingual ASR and translation across six languages.
  • Kakao kanana-2-30b-a3b-instruct enables bilingual agentic AI capabilities.
  • OpenFold3 provides high-performance biomolecular structure prediction.
  • All models are immediately deployable via SageMaker JumpStart.
TRADE-OFFNew SageMaker ModelsGranite SpeechMultilingual speech recognitionSix languages supportedKanana 2Bilingual agentic workflows30 billion parametersvs

Researchers propose OrchSLM, a non-interactive orchestration paradigm that combines heterogeneous small language models to handle agentic subtasks. This approach addresses the latency, privacy, and cost constraints of large cloud-based models while mitigating SLM limitations in long-horizon reasoning. The study probes the dynamics of this complementary architecture as an alternative to interactive debate or iterative verification strategies.

  • SLMs offer lower latency and better privacy for repetitive agentic subtasks compared to monolithic LLMs.
  • OrchSLM uses a non-interactive, heterogeneous model pipeline to overcome SLM context window limits.
  • This paradigm avoids the overhead of iterative verification and debate required by smaller models.
  • Specialized SLMs may outperform general LLMs on narrowly scoped tasks in agentic workflows.
  • The approach aims to reduce computational costs while maintaining reasoning capabilities.
HOW IT WORKSOrchSLM Pipeline Stages1Decompose agentic task2Assign subtasks to SLMs3Run models in parallel4Aggregate results non-interactively

AWS has integrated TwelveLabs Marengo 3.0 into Amazon Bedrock Managed Knowledge Base, enabling direct multimodal embeddings for video, audio, and images. Unlike previous text-only approaches that relied on transcription, Marengo 3.0 encodes visual scenes and speech cues directly into compact 512-dimensional vectors. This allows for natural language search across media assets with state-of-the-art retrieval accuracy and precise segment timing.

  • Marengo 3.0 enables direct multimodal embedding of video, audio, and images in Bedrock KB.
  • Captures visual and audio semantics beyond what transcription-based text embeddings provide.
  • Produces compact 512-dimensional vectors for efficient storage and high-accuracy retrieval.
  • Supports natural language search with precise start/end segment results for media assets.
BY THE NUMBERSCompact Vector Dimension512Dimensions for multimodal vectorsCompact vectors for efficient storage and high-accuracy retrieval

Agentic AI 7

roundup ↗

Grab has deployed LLM-Kit, an internal framework that standardizes and manages over 500 AI agent services. The system centralizes infrastructure, tool discovery, and secret handling, drastically reducing deployment time from two weeks to one hour. This approach allows for flexible model integration while maintaining strict operational control across the fleet.

  • Standardizes 500+ internal agent services to reduce fragmentation.
  • Cuts deployment cycle from two weeks to one hour via automation.
  • Centralizes secret handling and evaluation for consistent security.
  • Enables runtime tool discovery without sacrificing operational control.

AWS has launched a new interface that allows users to interact with AI agents using an email-like paradigm. The tool, exemplified by the 'Pizza Bot' demo, enables local execution of agents while providing a familiar inbox-style experience for receiving reports and posing questions. This approach aims to streamline communication between human operators and autonomous AI systems.

  • AWS now supports an email-style UI for managing AI agent interactions.
  • Agents can run locally while maintaining a centralized inbox interface.
  • Simplifies reporting and querying for AI workflows with familiar UX.
  • No direct database infrastructure changes required for this feature.
  • Focuses on human-agent communication rather than backend scaling.

IBM Research introduces a method to verify if large language model agents can reliably repeat successful tasks rather than relying on luck. The approach leverages adaptive learning techniques to stabilize agent behavior across multiple runs. This addresses the common issue where agents perform well in isolation but fail to maintain consistency in production workflows.

  • Agents often succeed by chance; this work focuses on repeatable reliability.
  • Uses adaptive learning to stabilize decision-making paths in LLM agents.
  • Critical for production systems requiring deterministic outcomes.
  • Reduces evaluation noise when testing agent performance over time.

As AI agents execute longer tasks, their execution logs become too large for manual review, making automated root-cause attribution (RCA) essential. Current LLM-based RCA methods struggle with low accuracy because relevant failure signals are sparse and distributed across distant actions in the trace. This research reframes RCA as a continual search problem to better locate these disconnected clues within massive execution histories.

  • Long-horizon agent logs are too large for human review, automating RCA is mandatory.
  • Standard LLM RCA fails on sparse, distributed signals across long execution traces.
  • Reframing RCA as a search problem improves diagnostic accuracy for complex agents.
  • One-shot LLM judgments are insufficient for tracing failures in multi-step tasks.
HOW IT WORKSReframing RCA as Search1Execute long-horizon agent tasks2Generate massive execution traces3Identify sparse failure signals4Search for root causes5Automate diagnostic attribution

OdoBot is a new web-agent architecture that significantly reduces token processing costs compared to conventional agents. It achieves this efficiency by constructing a behavioral model of the target application derived from successful task-execution demonstrations. Validated on 45 tasks within the Canvas Learning Management System, the approach demonstrates that leveraging application behavior patterns can lower operational expenses.

  • Leverage behavioral models from past successes to optimize future agent runs
  • Web agents can reduce token overhead by encoding application-specific patterns
  • Canvas LMS experiments confirm cost savings across 45 distinct tasks
  • Shift from brute-force UI analysis to behavior-guided execution strategies
BY THE NUMBERSTask Validation Count45Canvas LMS tasks validatedBehavioral modeling reduces token costs

A new agentic system addresses supply chain analytics complexity by using a coordinator agent to interpret user intent and delegate tasks to specialized sub-agents. This architecture supports both exploratory analysis and deterministic workflows, allowing planners to seamlessly switch between ad hoc queries and structured processes. The framework aims to bridge the gap between business decision-making and the technical expertise required for database querying, KPI analysis, and forecasting.

  • Coordinator agent delegates sub-tasks to specialized agents, reducing the need for cross-functional expertise.
  • Supports both ad hoc exploratory analysis and deterministic workflows for flexible planning.
  • Integrates database querying, KPI analysis, and demand forecasting into a unified agentic interface.
  • Aims to lower the barrier for planners to execute complex data engineering and operations research tasks.
HOW IT WORKSAgentic Supply Chain Workflow1Planner states business intent2Coordinator agent interprets request3Specialized agents execute tasks4Unified interface delivers results

Alex Porcelli addresses the accountability risks of non-deterministic LLM outputs in high-stakes enterprise scenarios. The proposed architecture integrates DMN decision models with agent skills and NeMo guardrails to enforce deterministic behavior. This approach allows business leaders to control decision logic while engineers manage the underlying architectural governance.

  • Combine DMN models with LLMs to ensure auditable, deterministic outcomes in agentic workflows.
  • Use NeMo guardrails to enforce safety and compliance boundaries around agent actions.
  • Separate decision logic ownership (business) from architectural governance (engineering).
  • Mitigate non-deterministic output risks in high-stakes enterprise AI deployments.

Automation / DevOps / IaC 8

roundup ↗

Atlassian has introduced a method for automating root cause analysis in cloud-native environments by correlating metrics, logs, distributed traces, and service topology. This system generates ranked hypotheses to identify failure origins and trace their propagation paths. The approach aims to streamline incident response for large-scale infrastructure. The technique leverages cross-signal data to pinpoint issues without manual intervention.

  • Correlate metrics, logs, traces, and topology to automate RCA.
  • System outputs ranked hypotheses for faster failure identification.
  • Focuses on propagation paths in large-scale cloud-native incidents.
  • Reduces manual triage effort for SRE teams.
  • Leverages service topology context for accurate root cause ranking.

AWS has integrated Amazon Q Console with CloudTrail to enable natural language investigation of API activity. Users can query logged events, check trail configurations, and identify logging gaps without writing code or parsing logs manually. This capability supports security audits and operational troubleshooting by allowing direct questioning of data sources and IAM role access.

  • Investigate CloudTrail events using plain English questions instead of writing queries.
  • Verify trail configurations and identify gaps in logging coverage automatically.
  • Troubleshoot operational issues and security concerns without manual log parsing.
  • Confirm which data event sources are currently being tracked by the trails.
CHECKLISTNew CloudTrail Investigation ActionsQuery events using plain EnglishVerify trail configurations automaticallyIdentify logging gaps instantlyTroubleshoot without manual parsing

Jeremy Schneider details the challenges of generating Software Bill of Materials (SBOMs) for PostgreSQL extensions within containers by relying on AI agents. He outlines the specific structure of current CloudNativePG images and discusses maintaining a downstream fork to include Open Source code restricted by CNCF policies. The work involves tracking upstream build infrastructure and submitting patches to minimize merge conflicts while ensuring full inventory and provenance.

  • AI agents can struggle with complex SBOM generation for Postgres extension containers.
  • Current CloudNativePG images have a specific structure requiring careful inventory tracking.
  • A downstream fork allows inclusion of Open Source code banned by CNCF guidelines.
  • Patch management focuses on minimizing merge conflicts with upstream build infra.
HOW IT WORKSManaging Postgres Extension SBOMs1Track upstream build infrastructure2Submit patches to minimize conflicts3Maintain downstream fork for CNCF code4Ensure full inventory and provenance

Jeremy Schneider is enhancing the CNPG-Extensions project by integrating Software Bill of Materials (SBOM) and provenance attestations. This move aims to provide container image assurance, enable accurate license scanning, and facilitate vulnerability comparisons. The initiative also includes exploring Rust dependency management for pgrx extensions.

  • SBOMs and attestations improve container transparency and license compliance.
  • Provenance data helps scanners match software versions against vulnerability databases.
  • Project now supports Rust dependencies for pgrx extensions.
  • Addresses licensing constraints by shifting from the original 'Not-CNPG' joke project.

This paper addresses the 'attestation deficit' where organizations hold governance policies but cannot produce auditable evidence of enforcement quickly enough. It proposes an adaptive intelligence architecture designed to enforce AI policies in real-time. The analysis cites recent reports highlighting widespread gaps in access controls and agent-to-agent monitoring across enterprises.

  • Governance lags behind AI adoption due to an inability to generate timely, tamper-evident evidence.
  • Proposed architecture aims to close the gap between policy definition and real-time enforcement.
  • Empirical data shows 92% of breaches lack proper access controls, underscoring the urgency.
  • Only 17% of organizations currently have agent-to-agent monitoring coverage.
  • The framework seeks to make governance auditable within regulatory timelines.
COMPARISONCritical Gaps in AI GovernanceBreaches with poor access controls92%Orgs with agent-to-agent…17%
Hacker News (100+ points) general

Baseten Production GitHub Compromised via Harbor PAT

Attackers gained administrative control over Baseten's production GitHub organization by exploiting a leaked personal access token. The vulnerability originated from a Harbor container registry credential that was inadvertently exposed in Baseten's codebase or configuration. This breach allowed the threat actors to escalate privileges and take over critical infrastructure assets.

  • Audit all CI/CD and container registry tokens for unintended scope or exposure in repos.
  • Enforce strict least-privilege policies for personal access tokens in production environments.
  • Monitor for anomalous administrative actions on source control platforms immediately.
  • Rotate all potentially compromised credentials across the entire infrastructure stack.
LangChain Releases agentsreleases ↺ since 09-12

LangChain Core 1.6.3 Enables Model Provider Tracing Override

LangChain Core 1.6.3 introduces the ability to override model name and provider tracing metadata based on gateway responses, allowing for more accurate observability in routed LLM calls. The release also adds test coverage for the deprecated .text() access path and cleans up stale documentation entries for FileCallbackHandler and ChatGeneration.

  • Gateway responses can now dynamically override tracing metadata for model name and provider.
  • Observability stacks will reflect the actual provider used rather than just the client endpoint.
  • Deprecated .text() access paths are now covered by tests to prevent silent regressions.
  • Stale Args/Raises docstrings removed from FileCallbackHandler and ChatGeneration.
  • Upgrade to 1.6.3 to enable dynamic provider tracing without custom instrumentation.
AWS What's New awsdatabase ↺ since 09-12

AWS DevOps Agent adds bidirectional Slack communication for incident response

AWS DevOps Agent now allows engineers to manage production operations across AWS, multicloud, and on-premises environments directly within Slack. This update consolidates incident investigation and communication into a single thread, eliminating the need to context-switch between platforms. Teams can initiate investigations by @mentioning the agent in private channels, with all findings and actions captured there.

  • Consolidates incident response and investigation tools into Slack to reduce context switching.
  • Supports operations across AWS, multicloud, and on-premises environments.
  • Enables bidirectional communication via @mentions in private Slack channels.
  • Captures all agent findings, team context, and recommended actions in a single thread.
HOW IT WORKSSlack Incident Response Flow1Engineer @mentions agent in Slack2Agent investigates across environments3Findings and actions in thread4Team collaborates in single view

AWS 7

roundup ↗

AWS has launched Amazon Linux 2027 in public preview, upgrading to kernel 7.1 and switching SELinux to enforcing mode as the default. This shift means applications that previously operated under AL2023's permissive policy will likely fail to start or function correctly. The announcement provides no specific dates for general availability or end-of-support for AL2023, nor does it outline an in-place migration strategy.

  • AL2027 defaults to SELinux enforcing, unlike AL2023's permissive stance.
  • Apps relying on permissive policies will break immediately upon migration.
  • Kernel is upgraded to version 7.1 in this new preview release.
  • No GA date, EOL date, or in-place migration path has been announced.
  • Test workloads against AL2027 now to identify SELinux compliance gaps.

AWS now distributes root user sign-in traffic across US East (N. Virginia), US East (Ohio), and US West (Oregon), reducing single-region dependency. The service automatically routes requests to a healthy region without user intervention. CloudTrail ConsoleLogin events for root users are now logged in the specific Region that processed the authentication request.

  • Root sign-in is now resilient across three US East and West regions.
  • Traffic routing is automatic; no user action is required for sign-in.
  • CloudTrail logs root events in the processing region, not just Virginia.
  • Update monitoring and alerting to cover all three regions for full visibility.
  • This change applies to all AWS accounts and is available immediately.
HOW IT WORKSResilient Root Sign-In1User initiates root login2AWS routes to healthy region3Authentication processed automatically4CloudTrail logs in region

Dropbox leverages a decade of infrastructure optimization to handle surging AI demand without relying solely on new data center capacity. Their strategy focuses on forecasting, fleet utilization, storage density, and hardware lifecycle management. This approach allows them to absorb growth by maximizing existing resources rather than just expanding physical footprint.

  • AI demand is absorbed through efficiency, not just new capacity.
  • Forecasting and fleet utilization are key to managing load.
  • Storage density and hardware lifecycles drive long-term savings.
  • Rack-level power delivery optimization supports higher compute.
  • Decade-long optimization predates current AI boom trends.

Intel spin-off Cornelis and startup Delos Data are introducing open alternatives designed to scale AI workloads beyond individual racks. These solutions aim to break the dependency on Nvidia's proprietary NVLink interconnect technology. The move signals growing competition in the high-speed fabric layer essential for large-scale distributed AI training.

  • Cornelis and Delos Data are targeting the rack-scale AI networking gap left by NVLink.
  • Open alternatives could reduce vendor lock-in for hyperscalers building massive clusters.
  • Competition may drive down costs and improve interoperability in AI infrastructure.
  • This shift challenges Nvidia's dominance in the high-performance interconnect market.
AWS What's New awsdatabase

AWS Adds Detected Anomalies Widget to Billing Dashboards

AWS has introduced a Detected Anomalies widget for Billing and Cost Management Dashboards, unifying cost tracking with anomaly detection. The widget displays the count and total cost impact of anomalies relative to month-to-date spend, while allowing users to drill into root causes and duration. Users can configure the view with 30, 60, or 90-day look-back periods and filter by severity, service, account, and region.

  • Centralize cost, usage, and anomaly data in a single dashboard view.
  • Filter anomalies by service, account, region, and severity for targeted analysis.
  • Review root cause and duration details directly within the widget.
  • Select 30, 60, or 90-day look-back periods to assess trend context.
CHECKLISTOptimize Anomaly DetectionCentralize cost and anomaly data in one viewFilter by service, account, region, and severityReview root cause and duration details directlySelect 30, 60, or 90-day look-back periods
AWS What's New awsdatabase

AWS Glue zero-ETL now captures archived Salesforce records

AWS Glue zero-ETL integrations for Salesforce have been updated to include archived records in target tables, ensuring a complete data replica for analytics. The isArchived field accurately reflects the status of records, maintaining synchronization between the analytical store and the Salesforce source. This update automatically applies to new integrations and backfills existing ones without requiring manual intervention.

  • Zero-ETL Salesforce jobs now include archived records for complete analytics coverage.
  • The isArchived field tracks status, keeping analytical data in sync with Salesforce.
  • No action required; new integrations capture archived data automatically from creation.
  • AWS Glue automatically backfills archived records for existing integrations.
CHECKLISTZero-ETL Salesforce UpdatesArchived records now included in target tablesisArchived field maintains sync with sourceNew integrations capture data automaticallyExisting jobs backfill archived records automatically

AWS Glue zero-ETL integrations now track which integration owns the properties of a target table, preventing silent collisions between multiple pipelines. This feature enforces isolation by detecting conflicts when different integrations attempt to write to the same destination catalog. Users are guided to either select a new target or update the existing integration, ensuring predictable data landing across S3 Tables and SageMaker Lakehouse.

  • Prevents multiple zero-ETL integrations from silently overwriting the same target table
  • Tracks ownership of table properties to the specific integration that created them
  • Validates conflicts at creation or modification time for S3 Tables and SageMaker Lakehouse
  • Guides users to resolve conflicts by choosing different targets or updating existing configs
  • Ensures data pipelines remain isolated and land exactly where intended
CHECKLISTZero-ETL Conflict PreventionTrack ownership of target table propertiesDetect conflicts during creation or modificationEnsure pipeline isolation for S3 TablesResolve collisions by updating configs or targets

Oracle Ecosystem 1

roundup ↗

Percona and HexaCluster have formed a partnership aimed at reducing the risk and timeline of migrating away from proprietary databases like Oracle, SQL Server, DB2, and Sybase ASE. The collaboration combines Percona’s open source distributions, operators, and enterprise support with HexaCluster’s assessment and migration engineering capabilities. This joint offering is designed to provide a predictable timeline without requiring extensive multi-year consulting engagements.

  • Partnership targets migration from Oracle, SQL Server, DB2, and Sybase ASE to open source alternatives.
  • HexaCluster provides the assessment and engineering layer for the migration process.
  • Percona supplies the underlying open source distributions, operators, and enterprise support.
  • Goal is to eliminate multi-year consulting programs in favor of predictable timelines.
HOW IT WORKSOracle Migration Partnership1HexaCluster assesses legacy databases2HexaCluster engineers migration path3Percona provides open source base4Percona delivers enterprise support

Trending on GitHub 8

roundup ↗
GitHub Trending (daily) githubrepos ⚠ unverified date/source

OmniGet: Open-source desktop downloader for 1,800+ sites using yt-dlp

OmniGet is a free, open-source desktop application that aggregates downloading capabilities for over 1,800 websites, including Udemy, Hotmart, YouTube, and social media platforms. Built on yt-dlp, it offers a graphical interface for Windows, macOS, and Linux, eliminating the need for terminal usage while keeping all files local. The app integrates tools for transcribing, converting, and reading content, such as a course player and PDF/EPUB reader, with no telemetry or ads.

  • Leverages yt-dlp engine for broad site support without terminal dependencies.
  • Local-first architecture ensures no telemetry or cloud storage of user data.
  • Includes built-in media players and readers for immediate content consumption.
  • GPL-3.0 licensed and free, positioning it as a privacy-focused alternative to commercial tools.
  • Currently trending with high GitHub stars, indicating strong community interest.
GitHub Trending (daily) githubrepos ⚠ unverified date/source

Ever Gauzy: Open ERP/CRM/HRM Platform with New Agentic Runtime

Ever Gauzy is an open-source business management platform covering ERP, CRM, HRM, and hiring workflows. The project now features Ever Works, an agentic runtime designed to autonomously research, ship, and maintain business operations around the clock. The frontend utilizes a React and Next.js stack, while the backend connects via headless APIs.

  • Full-stack open source alternative for ERP, CRM, and HRM needs
  • New Ever Works module introduces autonomous agentic business capabilities
  • Architecture pairs Next.js frontend with headless API backend
  • Targeted at collaborative, on-demand, and sharing economy models
GitHub Trending (daily) githubrepos ⚠ unverified date/source

DeskcommCRM: Open-source AI CRM with native WhatsApp agents and MCP readiness

DeskcommCRM is a self-hosted, multi-tenant CRM designed to replace platforms like Kommo and Intercom for chat-based sales. It features native AI agents that handle customer interaction and qualification directly within WhatsApp via WAHA. The system is built with data sovereignty in mind, supporting LGPD compliance and offering multi-language capabilities.

  • Self-hosted architecture ensures data privacy and eliminates per-seat licensing fees.
  • Native WhatsApp integration via WAHA allows AI agents to qualify leads autonomously.
  • MCP-ready design facilitates future integration with broader AI agent ecosystems.
  • Multi-tenant support enables secure deployment for agencies or large enterprises.
  • One-command production setup available through HostGator partner kit.
TRADE-OFFDeskcommCRM vs Traditional CRMsTraditional PlatformsPer-seat licensing fees applyCloud-hosted data risksLimited native AI agentsDeskcommCRMSelf-hosted free architectureFull data sovereignty controlNative WhatsApp AI agentsvs
GitHub Trending (daily) githubrepos ⚠ unverified date/source

VoiceStudio offers local, no-API voice cloning and TTS across 646 languages

VoiceStudio is an open-source, fully-local alternative to commercial voice services, providing voice cloning, dubbing, and transcription without requiring accounts or API keys. The application leverages 16 TTS engines and 11 ASR engines to support audio production in 646 languages. It is available as a desktop app for macOS, Windows, and Linux, as well as via Docker, with an ongoing Electron rewrite.

  • Runs fully local with zero API keys or subscriptions, ideal for privacy-sensitive workflows.
  • Supports 646 languages using 16 TTS and 11 ASR engines for diverse audio tasks.
  • Deployable via Docker or native desktop apps on major OS platforms.
  • Currently in active beta; use latest release for stability during production work.
GitHub Trending (daily) githubrepos ⚠ unverified date/source

Homebrew launches official macOS GUI BrewUI for CLI-averse users

Homebrew has released BrewUI, an official native macOS application built with Swift 6.0 and SwiftUI. The tool provides a graphical interface for discovering and managing packages while maintaining full transparency over underlying CLI operations. It interacts directly with the brew CLI and Homebrew JSON API, ensuring users see exactly what is happening during installations and updates.

  • Native SwiftUI app targets macOS Tahoe 26+ for CLI-averse users
  • Maintains transparency by never hiding underlying Homebrew operations
  • Uses Swift 6.0 strict concurrency and Swift Package Manager
  • Launches brew via /bin/zsh with --no-rcs to disable shell startup files
TRADE-OFFBrewUI vs Traditional CLITraditional CLIRequires terminal knowledgeText-based interaction onlyBrewUI AppNative SwiftUI interfaceFull operation transparencyvs
GitHub Trending (daily) githubrepos ⚠ unverified date/source

OpenResearch turns coding agents into local-first research workflows

OpenResearch is a local-first workspace designed to transform CLI coding agents like Claude Code and Cursor into autonomous research agents. It enables users to review literature, develop hypotheses, and generate research artifacts by connecting local LLMs or custom endpoints. The tool provides a local dashboard for managing these automated research tasks on macOS and Linux.

  • Wraps coding agents (Claude Code, Cursor) into research workflows for literature review and hypothesis generation.
  • Supports local LLM integration via LM Studio, Ollama, or custom endpoints for privacy and control.
  • Runs locally with a web dashboard at 127.0.0.1:4791, requiring no cloud dependency for core features.
  • Simplifies setup via a single CLI installer script for macOS and Linux environments.
HOW IT WORKSLocal Research Pipeline1Install CLI script2Select local LLM3Review literature4Generate hypotheses5Create artifacts
GitHub Trending (daily) githubrepos ⚠ unverified date/source

NSA Ghidra SRE Framework: Cross-Platform Analysis and Decompilation

The National Security Agency maintains Ghidra, an open-source software reverse engineering framework supporting Windows, macOS, and Linux. It provides advanced capabilities such as disassembly, decompilation, and graphing for diverse processor instruction sets and executable formats. The tool operates in both interactive and automated modes, allowing users to extend functionality via Java or Python scripts.

  • Full SRE suite including decompiler and graphing for multi-platform binaries.
  • Extensible architecture supports custom modules via Java or Python APIs.
  • Automated mode enables integration into CI/CD or batch analysis pipelines.
  • Broad ISA support covers common and exotic processor instruction sets.
GitHub Trending (daily) githubrepos ⚠ unverified date/source

Atlas: Source control for coding agents with queryable checkpoints

Atlas provides version control specifically for AI coding agents like Claude Code and Codex. It captures detailed checkpoints for every agent run, linking commits to the original session, prompts, tool calls, and reasoning logic. This allows engineers to track exactly which agent made which changes and why, supporting multiple agents working on the same codebase with shared memory.

  • Track agent changes by linking commits to specific sessions, prompts, and tool calls.
  • Run multiple coding agents side-by-side on the same codebase without losing context.
  • Query agent history months later to understand the 'why' behind code changes.
  • Supports Claude Code, Codex, and agents from the ACP registry.
  • Shared memory allows switching agents mid-task without starting over.
↑