# service Published articles for service. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Systemtap 5.6 released DevFeed: [Systemtap 5.6 released]() Original publisher: [Read original article]() Author: corbet Published: 2026-09-18T12:58:42Z Content type: release Language: en Sources: [LWN.net]() Topics: [tracing](), [Kernel](), [Linux](), [processing](), [systemd](), [hooks]() Tags: [hooks](), [kernel](), [linux](), [processing](), [service](), [systemd](), [tracepoint](), [tracing](), [version]() ### AI overview SystemTap 5.6 has been released with new BPF LSM and XDP probes, BTF-based kernel tracepoint probes, statement execution tracing, improved runtime error context, dyninst hardware watchpoints, updated systemd service templates, Linux 7.2 compatibility work, and multithreaded performance improvements. ### Source excerpt Version 5.6 of the Systemtap tracing tool has been released. BPF LSM hooks and XDP packet-processing probes for the --bpf runtime, BTF-based kernel.tracepoint probes, statement execution tracing, a new @enumname() operator, richer runtime error context, dyninst hardware watchpoints, modern systemd service templates, and broad Linux 7.2 runtime/tapset compatibility work. Multithreaded speedups throughout. ## ML based ranking using Nrtsearch DevFeed: [ML based ranking using Nrtsearch]() Original publisher: [Read original article]() Author: Mohammad Mohtasham (Software Engineer); Tao Yu (Software Engineer) Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [Inference](), [Scalability](), [Latency](), [recommendation systems](), [Open Source]() Tags: [bridge](), [inference](), [machine-learning](), [overhead](), [performance](), [pipeline](), [scalability](), [service]() ### AI overview Yelp's Nrtsearch Inference Plugin embeds machine-learning ranking directly in the search layer. The article explains the scoring workflow, including model configuration, feature extraction, candidate ranking, and application-specific business logic. It describes how co-locating feature storage and inference reduces network transfer, serialization overhead, and latency compared with a standalone inference service. ### Source excerpt We've extended Nrtsearch with the Inference Plugin, which embeds ML-based ranking directly in the search layer -- eliminating the need for a standalone scoring service. We use Nrtsearch (read more information on the blog post), a Lucene-based open-source search engine built by Yelp, to power a variety of applications such as business search, reviews search, ad delivery and photo search. In this blog post, we give a high-level overview of the Machine Learning (ML) based scoring workflow in Nrtsearch. We'll show how ML models are configured and loaded, and how different applications use custom business logic to develop, test, and... ## Every service needs an owner DevFeed: [Every service needs an owner]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-09-12T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [systems](), [incident]() Tags: [catalog](), [customer](), [incident](), [on-call](), [ownership](), [platform-engineering](), [production](), [reliability](), [service](), [service-catalog](), [sre](), [startups](), [team]() ### AI overview The article argues that growing organizations need a focused service catalog to make production ownership visible. It recommends recording each service's customer outcome, owning team, current on-call contact, deployment path, health dashboard, runbook, and dependencies, and maintaining those records as part of engineering work. ### Source excerpt A useful service catalog is not an inventory project. It is a public record of who owns a customer outcome when the system is healthy and when it fails. ## NFR Brain: challenging the status quo of risk management with data DevFeed: [NFR Brain: challenging the status quo of risk management with data]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-04T14:18:41Z Content type: article Language: en Sources: [Nubank]() Topics: [risk-management](), [data](), [Resilience](), [incident]() Tags: [business](), [complexity](), [data](), [data-analytics](), [data-science-machine-learning](), [management](), [resilience](), [risk](), [risk-management](), [service]() ### AI overview Nubank is building NFR Brain, a platform that combines data, modelling and expert judgement to create a comparable and actionable view of non-financial risk. The article explains how the platform is intended to support clearer, more consistent prioritization across operational failures, customer complaints, third-party dependencies and other risk signals. ### Source excerpt Author : Mayara Zenati At Nubank, we believe the most meaningful problems for customers and for the business rarely come with ready-made answers. That is why we challenge the status quo: not to innovate for innovation's sake, but to remove complexity and build solutions that make important decisions simpler, faster and better. This mindset also [...] The post NFR Brain: challenging the status quo of risk management with data appeared first on Building Nubank. ## Why Senior Leaders Should Attend Post-Incident Reviews for Major Cloud Incidents DevFeed: [Why Senior Leaders Should Attend Post-Incident Reviews for Major Cloud Incidents]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-29T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [incident](), [Cloud](), [control-plane](), [Deployment]() Tags: [cloud](), [control-plane](), [customers](), [deploy](), [incident](), [incident-management](), [leadership](), [major](), [operations](), [post](), [postmortems](), [reliability](), [review](), [service]() ### AI overview The article argues that senior leaders should attend Post Incident Reviews for major cloud incidents because failures can affect many customers and teams. Leadership helps approve cross-team changes, resolve trade-offs, and ensure corrective actions are completed. ### Source excerpt For major incidents, a Post Incident Review is not an operations meeting. It is where leaders remove the blockers that keep the service from becoming safer. ## Welcoming the Sri Lankan Government to Have I Been Pwned DevFeed: [Welcoming the Sri Lankan Government to Have I Been Pwned]() Original publisher: [Read original article]() Author: Troy Hunt Published: 2026-08-23T06:39:45Z Content type: news Language: en Sources: [Troy Hunt]() Topics: [monitor](), [service](), [data]() Tags: [cyber](), [data](), [data-breaches](), [government](), [have-i-been-pwned](), [monitor](), [public-sector](), [service](), [visibility]() ### AI overview Have I Been Pwned has onboarded Sri Lanka as its 48th government customer for the free HIBP service. Sri Lanka CERT can monitor government domains for exposed accounts and respond to new data breaches. ### Source excerpt Today, we welcome the 48th government onboarded to Have I Been Pwned's free gov service: Sri Lanka. Sri Lanka CERT now has access to monitor Sri Lankan government domains against the data in HIBP, helping identify exposed government accounts and respond when they appear in new data breaches. ## LibreQoS 2.2 is out DevFeed: [LibreQoS 2.2 is out]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-20T15:11:31Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [changelog](), [Network](), [service](), [browser](), [interface](), [sessions](), [API]() Tags: [2-2](), [api](), [browser](), [changelog](), [improvements](), [interface](), [libreqos](), [network](), [network-engineering-resources](), [service](), [sessions]() ### AI overview This changelog describes LibreQoS 2.2, released on August 18, 2026, and its changes since version 2.1. It covers browser-based installation and setup, visual topology building, subscriber shaping from RADIUS sessions, traffic comparisons, and related improvements to LibreQoS Insight and the paid LibreQoS API. ### Source excerpt LibreQoS 2.2 ChangeLog LibreQoS 2.2: What Changed Since 2.1 LibreQoS 2.2 guides operators from a fresh install through admin creation, interface selection, network preview, and service startup in the browser. Operators can build topology visually, shape subscribers created from RADIUS sessions, and compare queued demand with traffic that actually crossed the wire. This changelog covers ... Read more The post LibreQoS 2.2 is out appeared first on Justin Wilson (j2sw). ## 【Istio 控制面】Linkerd 对照：非 xDS 的控制面机制 DevFeed: [【Istio 控制面】Linkerd 对照：非 xDS 的控制面机制]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-11T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [istio](), [linkerd](), [API](), [proxy]() Tags: [api](), [control-plane](), [destination-controller](), [envoy](), [go](), [identity](), [istio](), [istiod](), [kubernetes](), [linkerd](), [mechanism-comparison](), [network](), [policy](), [proxy](), [route](), [rust](), [service](), [serviceaccount](), [sidecar](), [xds]() ### AI overview This article compares Linkerd's control-plane architecture with Istio's istiod and xDS model. It describes Linkerd's separately deployed destination, identity, and proxy-injector components; its proxy-specific gRPC APIs; and its CSR-based identity issuance, contrasting these with Istio's consolidated control plane and xDS/SDS resource model. It explicitly avoids declaring either system superior without workload-specific evidence. ### Source excerpt 以官方文档为准，对照 Linkerd destination/identity 控制面与 Istio istiod/xDS 的机制差异：资源模型、订阅形状、身份签发路径；只讲机制边界，不判定优劣。 ## History of SpaceX: The Category-Dominating Commercial Spinoff and the Internalization of Anchor Demand DevFeed: [History of SpaceX: The Category-Dominating Commercial Spinoff and the Internalization of Anchor Demand]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-04T09:00:00Z Content type: article Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [communications](), [Deployment](), [service]() Tags: [aerospace](), [beta](), [business](), [capacity](), [customer](), [deployment](), [history](), [international](), [launches](), [operational](), [partnership](), [regulatory](), [revenue](), [service](), [spacex](), [subscriber]() ### AI overview This article examines SpaceX's commercial spinoff as the internalization of an anchor customer. It explains how the spinoff consumes the parent's launch output at marginal cost, traces its deployment, service rollout, integration, subscriber and revenue development, direct-to-cell expansion, capital requirements, and regulation, and compares the configuration with other satellite-constellation businesses. ### Source excerpt This article is the eleventh in the History of SpaceX series and the third and last treating the capital-formation legs that the series opener introduced. The category-dominating commercial spinoff concerns the business the venture built on top of its own capability, and the article's organizing claim is that the spinoff is not a diversification into an adjacent market but the internalization of an anchor customer. Where the Anchor Demand article A283 treats a government customer buying launches, this article treats the venture becoming the customer it had previously needed someone else to be. The decisive economic property is not that the spinoff grew large. It is that the spinoff consumes the parent's output at marginal cost while every competitor attempting the same business must pay a market price the parent sets. The article walks the January 2015 announcement and the capacity argument that motivated it, the deployment sequence from the first operational batch of May 2019 through the service beta of 2020 and the commercial rollout of 2021, the vertical integration and the internal transfer price that the whole arrangement turns upon, the coupling between constellation deployment and launch cadence, the subscriber and revenue trajectory across the 2020 through drafting-date period, the direct-to-cell extension beginning with the carrier partnership announced in 2022, the capital intensity and the replenishment obligation that a short-lifetime constellation imposes, and the regulatory position across the Federal Communications Commission, the International Telecommunication Union, and the national regulators whose authorizations the service requires. The article contrasts the configuration against the Iridium and Globalstar precedents, in which comparable constellations were built without a captive launch capability, and against the OneWeb and Kuiper cases, in which competitors attempted the business while buying launch at market. The article closes with an expli ## OpenTK: nu ook met Internetconsultaties & notificaties DevFeed: [OpenTK: nu ook met Internetconsultaties & notificaties]() Original publisher: [Read original article]() Published: 2026-07-20T11:37:00Z Content type: release Language: nl Sources: [Bert Hubert's writings]() Topics: [data](), [context](), [email]() Tags: [email](), [service]() ### AI overview OpenTK has added Internet consultations to opentk.nl, including them in its search engine and notification service. The article explains that Internet consultations are an early public stage in the development of new laws or regulations. ### Source excerpt Sinds 2024 run ik OpenTK, met als doel zo goed mogelijk te laten zien wat er in de Tweede Kamer allemaal gebeurt. En, om daar ook nuttige email-notificaties over te versturen. OpenTK is begonnen omdat ik (vanuit de Internetwereld) ineens geconfronteerd werd met een wet die over DNS (mijn hobby) ging en over een paar dagen in stemming zou komen. Dat was heel erg schrikken en ik dacht, dat kan ons nooit meer gebeuren. ## What Interviewers Listen for in Behavioral Interviews DevFeed: [What Interviewers Listen for in Behavioral Interviews]() Original publisher: [Read original article]() Author: Stephane Moreau Published: 2026-07-19T11:12:27Z Content type: tutorial Language: en Sources: [Blog for Engineering Managers]() Topics: [Job](), [incident](), [service](), [connection pool]() Tags: [connection-pool](), [engineering](), [guide](), [how-to](), [incident](), [influence](), [interviews](), [junior](), [scope](), [service](), [teams]() ### AI overview This article explains how interviewers assess behavioral answers, emphasizing the scope of ambiguity, influence across teams, trade-offs, and whether candidates actively discovered problems. It argues that these signals can distinguish mid-level engineers from Staff-level engineers before the stated outcome. ### Source excerpt What I'm actually listening for when you answer. ## Invite Systems are an Open Relay DevFeed: [Invite Systems are an Open Relay]() Original publisher: [Read original article]() Author: Josh Sherman Published: 2026-07-19T00:00:00Z Content type: opinion Language: en Sources: [Josh Sherman]() Topics: [systems](), [email](), [Monitoring]() Tags: [email](), [monitoring](), [server](), [service](), [user]() ### AI overview The article explains how invite systems can be abused for spam when users control organization names and platforms fail to limit invitation volume. It recommends sensible invite caps and monitoring for users who reach them. ### Source excerpt Every time I think I've seen it all from spammers, they do something that surprises me. The ingenuity of bad actors is an interesting thing. I always wonder what sort of world we'd live in if their efforts were focused on good. What sucks the most is when they abuse something that's intended to bring people together. Case in point, an invite system. It exists to allow somebody the chance to get the rest of their team using a product or service. Invites wouldn't work if they said "You've been invited to platform" with no additional context. Typically the email states the name of the organization you're being invited to. "You've been invited to your organization name here". Where does that organization name come from? The user of course! And what happens if the user has ill intentions? They set the organization name to something like "Text 1-800-555-1212 for a good time", or something even sketchier than that. Generally speaking, these emails come through transactionally and from a generic email on the platform. If your system doesn't meter the number of invites, you have yourself a certified spam cannon! May as well set up an SMTP server without authentication, better known as an open mail relay. There's a few ways you can approach limits. Have a cap on the total number of pending invites? The spammer may delete pending invites to keep moving. Daily limits on total invites sent? Maybe they'll be okay with stretching their campaign over days? Probably not, most spammers are in the business of going as hard and fast as possible before they get caught. Occasionally somebody will fly below the radar, but I think that's more of a bug than a feature. Sane limits as to not get in the way of legitimate users tends to get you pretty far. Monitoring if/when somebody hits the limits is good too. Spammers usually won't write in to let you know they hit some limit. I say usually because there are some special folks out there that will come knocking. ## Weekly Update 511: The limits of services that remove data from brokers DevFeed: [Weekly Update 511: The limits of services that remove data from brokers]() Original publisher: [Read original article]() Author: Troy Hunt Published: 2026-07-08T13:54:46Z Content type: opinion Language: en Sources: [Troy Hunt]() Topics: [data](), [service]() Tags: [data-breaches](), [marketing](), [service](), [update](), [weekly-update]() ### AI overview This weekly commentary discusses data breaches and the limits of services that try to remove personal information from legally operating data brokers. It also criticizes the marketing behind those services and their product-placement outreach. ### Source excerpt How's this for a location?! I mean, last week was nice with Scott in Mallorca, but Marrakech is, well, wow 😮 Anyway, about those data breaches... This week I'm talking about the futility of attempting to remove piss from a pool, yet here we are, with ## Don't forget Google SAS retires June 2027. DevFeed: [Don't forget Google SAS retires June 2027.]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-23T19:34:33Z Content type: news Language: en Sources: [Justin Wilson (j2sw)]() Topics: [SAS](), [Google](), [Google Cloud Platform (GCP)](), [migration](), [service]() Tags: [2026](), [3ghz](), [cbrs](), [cloud](), [deployments](), [existing](), [google](), [google-cloud](), [migration](), [net-11](), [network-operations](), [operational](), [retirement](), [sas](), [service](), [wireless-networking]() ### AI overview Google Cloud Spectrum Access System (SAS) is being retired. It stopped accepting new customers on June 10, 2026, will remain operational for existing customers during the transition, and is scheduled to shut down on June 10, 2027. ### Source excerpt In case you forgot: RETIREMENT NOTICE Google Cloud Spectrum Access System (SAS) is being retired. Starting June 10, 2026, we are no longer accepting new customers. The service will remain fully operational for existing customers during the transition period and will be shut down on June 10, 2027. Please review the migration steps below for instructions on ... Read more The post Don't forget Google SAS retires June 2027. appeared first on Justin Wilson (j2sw). ## How we shipped 15 Tbps for OpenAI in 90 days (Session 1 of 3) DevFeed: [How we shipped 15 Tbps for OpenAI in 90 days (Session 1 of 3)]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-06-08T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [cloud-infrastructure](), [Network architectures](), [Network Configuration](), [OpenAI]() Tags: [architecture](), [gpu](), [network](), [network-configuration](), [object-storage](), [openai](), [platform-engineering](), [production](), [region](), [scale](), [service](), [sre](), [storage](), [teams]() ### AI overview Session 1 describes how a team closed the architecture for OpenAI's second Object Storage instance in the same physical region as its primary. The production system was designed for 15 Tbps of GPU-fleet traffic and a three-month delivery timeline, with major architecture decisions completed in one week. ### Source excerpt OpenAI wanted a second Object Storage instance, in customer-facing production, at 15 Tbps, in three months. Session 1 covers the first week: closing the architecture. ## Track customer loyalty points with durable workflows DevFeed: [Track customer loyalty points with durable workflows]() Original publisher: [Read original article]() Author: Cecil Phillip Published: 2026-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [account](), [business logic](), [Database](), [real-time](), [locking](), [retry](), [service](), [upgrade](), [Mobile]() Tags: [account](), [business-logic](), [customer](), [database](), [locking](), [loyalty](), [loyalty-points](), [mobile](), [process](), [query](), [real-time](), [retry](), [service](), [temporal](), [temporal-concepts](), [upgrades](), [workflows]() ### AI overview This article explains how to track customer loyalty points with durable Entity Workflows in Temporal. Each customer has a persistent workflow that maintains points, tier status, and activity history, while Signals handle accruals, Updates validate redemptions, and Queries read current balances. ### Source excerpt Track loyalty points with durable Entity Workflows in Temporal. See how to handle accruals, tier upgrades, and redemptions for each customer. ## garnix is joining Shopify DevFeed: [garnix is joining Shopify]() Original publisher: [Read original article]() Published: 2026-05-28T00:00:00Z Content type: release Language: en Sources: [Garnix Blog]() Topics: [Shopify]() Tags: [open](), [service](), [shopify]() ### AI overview garnix is joining Shopify, while the garnix service is being shut down and its code is being open-sourced. ### Source excerpt We are open-sourcing garnix and shutting down the service. ## Storage at scale: what I actually watched DevFeed: [Storage at scale: what I actually watched]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-05-28T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [dashboards](), [site-reliability-engineering](), [Latency](), [Availability](), [control-plane](), [Databases](), [Replication]() Tags: [availability](), [control-plane](), [database](), [latency](), [metrics](), [reliability](), [replication](), [service](), [sre](), [storage]() ### AI overview An SRE practitioner describes seven metrics for judging the health of a large-scale storage service, covering availability, durability, latency, synthetic canaries, hotspots, IOPS, and metadata-database behavior. ### Source excerpt For eight years I ran SRE for a storage system measured in exabytes. The dashboard I checked every morning shrank to seven numbers. Here they are. ## Rate-limit downstream APIs with separate Task Queues DevFeed: [Rate-limit downstream APIs with separate Task Queues]() Original publisher: [Read original article]() Author: Cecil Phillip Published: 2026-05-25T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [rate-limiting](), [API](), [Concurrency](), [configuration]() Tags: [apis](), [concurrency](), [configuration](), [queues](), [rate-limiting](), [service](), [temporal-concepts]() ### AI overview This tutorial explains how to use separate Temporal Task Queues with global and optional per-Worker rate limits, plus concurrency limits, to keep Activities within downstream API quotas and help prevent 429 errors and account issues. ### Source excerpt Stop hitting 429s on downstream APIs. Use rate-limited Temporal Task Queues to keep Activities under SendGrid, Stripe, and OpenAI quotas. ## Service Levels: SLI, SLO, SLA DevFeed: [Service Levels: SLI, SLO, SLA]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-05-24T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [Availability](), [telemetry](), [Artificial Intelligence]() Tags: [ai](), [availability](), [rca](), [reliability](), [service](), [slo](), [sre](), [telemetry]() ### AI overview The article distinguishes SLI, SLO, and SLA as a hierarchy: measured reality, an internal target, and a customer contract. It explains how the gap between SLO and SLA creates an error budget and describes AI uses such as detecting SLO erosion, correlating telemetry, and drafting root-cause analyses while leaving operational judgment to engineers. ### Source excerpt What SLI, SLO, and SLA actually mean, why the order matters, and where AI helps. ## Digitale autonomie: wat kunnen organisaties NU doen DevFeed: [Digitale autonomie: wat kunnen organisaties NU doen]() Original publisher: [Read original article]() Published: 2026-05-21T11:30:00Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [Software as a service](), [cloud-infrastructure](), [data](), [datacenter](), [Server](), [servers](), [Software](), [service]() Tags: [analytics](), [autonomie](), [data](), [datacenters](), [marketing](), [privacy](), [servers](), [service](), [software](), [trackers]() ### AI overview This Dutch opinion article discusses practical steps organizations can take to improve digital autonomy after years of dependence on American big tech. It recommends stopping unnecessary migrations, retaining viable European-hosted systems, consulting internal critics of data transfers, and removing American trackers from websites and apps. ### Source excerpt De zorgen over digitale autonomie nemen toe, en steeds vaker krijg ik van (grote) organisaties de vraag: wat kunnen we NU doen? Nou heb ik wel een lijstje, maar voor we beginnen, besef dat we 15 jaar lang alles naar Amerika hebben geschoffeld. Of, we hebben het uitbesteed, en DIE mensen stuurden het naar Amerika. 15 jaar is een lange tijd, en we zijn niet 1 2 3 weer "in vorm" om de zaken weer anders aan te pakken. ## Ansible roles: proxy\_env, ssh, etc\_hosts, libvirt released DevFeed: [Ansible roles: proxy\_env, ssh, etc\_hosts, libvirt released]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2026-05-03T06:03:00Z Content type: release Language: en Sources: [stafwag Blog]() Topics: [Ansible Roles](), [releases](), [Ansible](), [ssh]() Tags: [ansible](), [apt](), [archlinux](), [changelog](), [debug](), [documentation](), [freebsd](), [kvm](), [libvirt](), [linux](), [pacman](), [releases](), [service](), [ssh]() ### AI overview The article announces releases for four Ansible roles: proxy_env 2.1.0, ssh 1.1.1, libvirt 2.1.0, and etc_hosts 1.1.1. It lists updates including package-management changes, handler fixes, documentation updates, lint corrections, and virtual-machine SSH host-key support. ### Source excerpt Made some time to do some work for a few Ansible roles that I maintain. You'll find the new releases below. ## How Agentic AI Creates Gaps in Audit-Trail Accountability DevFeed: [How Agentic AI Creates Gaps in Audit-Trail Accountability]() Original publisher: [Read original article]() Author: flashdba Published: 2026-04-27T13:43:04Z Content type: opinion Language: en Sources: [flashdba]() Topics: [AI Agent](), [audit trail](), [audit]() Tags: [account](), [agentic](), [agentic-ai](), [ai](), [ai-agent](), [audit](), [audit-trail](), [changes](), [cloud](), [commit](), [compliance](), [credentials](), [databases](), [databases-and-agentic-ai](), [identity](), [inferencing](), [model](), [performance](), [regulatory](), [service]() ### AI overview The article argues that conventional audit trails can record database changes accurately while failing to explain an AI agent's reasoning or establish accountable human ownership. It identifies unstable agent identity and the absence of externally documented reasoning as the central gaps. ### Source excerpt The audit trail still runs. Every commit is recorded. But agentic AI has broken the two assumptions it was built on - and the incompleteness is invisible until you need it. ## Btw: Software, turnkey, beheerd, as a service DevFeed: [Btw: Software, turnkey, beheerd, as a service]() Original publisher: [Read original article]() Published: 2026-03-13T11:43:53Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [Software](), [servers]() Tags: [servers](), [service](), [software](), [update]() ### AI overview The article discusses different ways organizations can have computers perform critical tasks, from self-programmed software to traditionally licensed software and software managed as a service. It focuses on the proposed outsourcing of the Dutch Tax Administration's VAT systems and the distinction between using American software and having the associated servers managed by Americans, while noting that the proposal ultimately did not proceed. ### Source excerpt De belastingdienst is van plan om de BTW uit te besteden aan een Amerikaans bedrijf, wat echt waanzinnig is. Op 19 maart is er een commissievergadering in de Tweede Kamer hierover, en ik hoop van harte dat men bij zinnen komt. UPDATE! Goed nieuws, ben is bij zinnen gekomen en het gaat niet door! In de discussie over de btw-situatie de afgelopen jaren ging het eigenlijk alleen over dat de belastingdienst Amerikaanse software ging gebruiken. [Next page]()