# datacenters Published articles for datacenters. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## HALEU production remains limited as Nusano says federal backing could accelerate supply for datacenters DevFeed: [HALEU production remains limited as Nusano says federal backing could accelerate supply for datacenters]() Original publisher: [Read original article]() Author: Brandon Vigliarolo Published: 2026-09-15T17:39:03Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [datacenter]() Tags: [datacenter](), [datacenters](), [haleu](), [nuclear-power](), [offbeat](), [smr]() ### AI overview HALEU production remains slow, while Nusano says federal backing could eventually accelerate supply for datacenters. ### Source excerpt HALEU is still being produced at a snail's pace; Nusano says its federal backing could speed things up - eventually ## America is building datacenters faster than the grid can power them DevFeed: [America is building datacenters faster than the grid can power them]() Original publisher: [Read original article]() Author: Dan Robinson Published: 2026-09-15T16:37:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [datacenter](), [systems]() Tags: [ai-and-ml](), [datacenters](), [energy](), [generation](), [on-prem](), [report]() ### AI overview Meeting expected energy consumption through 2030 will require $110 billion in new generation resources as America builds datacenters faster than the power grid can support. ### Source excerpt Meeting expected energy consumption through 2030 will require $110 billion in new generation resources ## Datacenter developers want your backyard. FAS says negotiate harder DevFeed: [Datacenter developers want your backyard. FAS says negotiate harder]() Original publisher: [Read original article]() Author: Dan Robinson Published: 2026-09-14T17:26:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [datacenter](), [on-prem]() Tags: [ai](), [community-benefits-agreements](), [data-center-policy](), [datacenter](), [datacenters](), [federation-of-american-scientists](), [infrastructure](), [on-prem](), [report]() ### AI overview A report advises local officials to negotiate carefully with datacenter developers before approving projects, focusing on tax breaks, water use, noise, and decommissioning obligations. ### Source excerpt Tax breaks, water, noise, decommissioning - report tells local officials what to nail down before signing ## Google takes the nuclear option for EUR 13B Finland expansion DevFeed: [Google takes the nuclear option for EUR 13B Finland expansion]() Original publisher: [Read original article]() Author: Dan Robinson Published: 2026-09-09T16:00:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Google]() Tags: [cloud](), [datacenters](), [finland](), [google](), [infrastructure](), [on-prem](), [renewable-energy]() ### AI overview Google's Finland expansion includes a 22-year power deal covering up to half of the Loviisa plant's capacity, alongside wind and battery projects. ### Source excerpt 22-year power deal covers up to half of Loviisa plant's capacity, with wind and battery projects alongside ## AI data centers: the five hard problems money cannot buy away DevFeed: [AI data centers: the five hard problems money cannot buy away]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-30T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [Artificial Intelligence](), [data centers](), [Hardware](), [systems]() Tags: [ai](), [capacity](), [compute](), [data-centers](), [datacenters](), [hardware](), [heat](), [infrastructure](), [power](), [reliability]() ### AI overview The article argues that AI data-center expansion is constrained by the simultaneous need to secure power, grid connections, cooling and water strategies, equipment, skilled workers, permits, and productive compute. It discusses five industry challenges, with the supplied text covering power constraints and the physical and water implications of liquid cooling. ### Source excerpt The AI buildout is not mainly a real-estate problem. It is a race to integrate power, cooling, equipment, permits, and useful compute at the same time. ## 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. ## What Does a Database for SSDs Look Like? DevFeed: [What Does a Database for SSDs Look Like?]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2025-12-15T00:00:00Z Content type: article Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [Databases](), [systems](), [cloud-infrastructure](), [datacenter](), [Latency]() Tags: [2025](), [cloud](), [database](), [databases](), [datacenter](), [datacenters](), [infrastructure](), [latency](), [mysql](), [network](), [networks](), [postgres](), [servers](), [sqlite](), [storage](), [systems]() ### AI overview The article examines how a relational database designed specifically for local NVMe SSDs might differ from databases created for spinning disks. It questions whether design choices such as write-ahead logging, large pages, bulk writes, and caching should change in light of faster storage, modern datacenter networks, abundant compute and memory, cloud infrastructure, and always-on global applications. It begins a quantitative analysis using the Five Minute Rule and 2025 hardware economics. ### Source excerpt What Does a Database for SSDs Look Like? Maybe not what you think. Over on X, Ben Dicken asked: What does a relational database designed specifically for local SSDs look like? Postgres, MySQL, SQLite and many others were invented in the 90s and 00s, the era of spinning disks. A local NVMe SSD has ~1000x improvement in both throughput and latency. Design decisions like write-ahead logs, large page sizes, and buffering table writes in bulk were built around disks where I/O was SLOW, and where sequential I/O was order(s)-of-magnitude faster than random. If we had to throw these databases away and begin from scratch in 2025, what would change and what would remain? How might we tackle this question quantitatively for the modern transaction-orientated database? But first, the bigger picture. It's not only SSDs that have come along since databases like Postgres were first designed. We also have the cloud, with deployments to excellent datacenter infrastructure, including multiple independent datacenters with great network connectivity between them, available to all. Datacenter networks offer 1000x (or more) increased throughput, along with latency in the microseconds. Servers with hundreds of cores and thousands of gigabytes of RAM are mainstream. Applications have changed too. Companies are global, businesses are 24/7. Down time is expensive, and that expense can be measured. The security and compliance environment is much more demanding. Builders want to deploy in seconds, not days. Approach One: The Five Minute Rule Perhaps my single favorite systems paper, The 5 Minute Rule... by Jim Gray and Franco Putzolu gives us a very simple way to answer one of the most important questions in systems: how big should caches be? The five minute rule is that, back in 1986, if you expected to read a page again within five minutes you should keep in in RAM. If not, you should keep it on disk. The basic logic is that you look at the page that's least likely to be re-used. If it's cheape ## Fixing UUIDv7 (for database use-cases) DevFeed: [Fixing UUIDv7 (for database use-cases)]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2025-10-22T00:00:00Z Content type: article Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [Databases](), [Caching](), [Security](), [Architecture & Design]() Tags: [cache](), [cryptographic](), [database](), [datacenters](), [performance](), [security]() ### AI overview The article examines UUIDv7 for database use cases, explaining how time ordering can improve index locality, insertion performance, and cache effectiveness while introducing concerns about timestamp leakage, reduced entropy, correlated behavior, and hot spotting. It proposes modifying UUIDv7 with a keyed hash, a tunable entropy parameter, and an infrastructure-specific identifier to balance locality with ID distribution. ### Source excerpt Fixing UUIDv7 (for database use-cases) How do I even balance a V7? RFC9562 defines UUID Version 7. This has made a lot of people very angry and been widely regarded as a bad move1. More seriously, UUIDv7 has received a lot of criticism, despite seemingly achieving what it set out to do. The legitimate criticism seems to be on a few points. V7 UUIDs: Leak information (namely the server timestamp). Are a bad choice for cases where security or operational requirements require UUIDs that are hard to guess, because they have less entropy. Introduce correlated behavior between datacenters, regions, and installations of applications, increasing the probability of triggering bugs across failure boundaries. Are hard to present in UIs, because the E6EE7F40... format doesn't work, because of deterministic first digits. Before thinking about how we might fix these issues, let's understand why folks are drawn to UUIDv7. Most of the use-cases I see are related to increasing database insert performance. To quote the RFC: Time-ordered monotonic UUIDs benefit from greater database-index locality because the new values are near each other in the index. As a result, objects are more easily clustered together for better performance. The real-world differences in this approach of index locality versus random data inserts can be one order of magnitude or more. This effect is very real. Random DB keys like UUIDv4 destroy spatial locality (as I've written about before), making database caches less effective, almost always reducing insert performance, and reducing query performance where queries have substantial temporal locality. The slight upside to this is that they also avoid hot spotting in distributed or sharded architectures. Can we both have good insert performance and avoid the downsides of UUIDv7? Yes, I believe we can. Let's keep the overall format from the RFC: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ## Dutch government plans broad migration of workplace and document management to Microsoft 365 DevFeed: [Dutch government plans broad migration of workplace and document management to Microsoft 365]() Original publisher: [Read original article]() Published: 2024-10-18T14:00:00Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [Microsoft](), [microsoft 365](), [Cloud](), [cloud-infrastructure](), [datacenter](), [data]() Tags: [autonomie](), [cloud](), [data](), [datacenters](), [microsoft](), [microsoft-365](), [nederlands](), [overheid](), [public](), [servers]() ### AI overview The article argues that nearly the entire Dutch national government, along with many municipalities and agencies, is moving workplace, document, and file management to Microsoft 365 and Microsoft's public cloud. It criticizes the concentration of government data and services with one US provider, citing legal, sovereignty, security, and outage concerns. ### Source excerpt Eerder deze week verscheen het rapport van de Auditdienst Rijk en daar staat het helder in: het is zo "dat straks (bijna) de volledige Rijksoverheid gebruik maakt van MS 365". En voor de zekerheid, verderop staat: "Hiermee wordt de on-premises werkplek van de Rijksoverheid verplaatst naar de public cloud [van Microsoft]". Het gaat dus gebeuren, de totale migratie van onze overheid naar MS 365, op Microsoft servers in Microsoft datacenters. ## Incident Summary: 2023-09-07 DevFeed: [Incident Summary: 2023-09-07]() Original publisher: [Read original article]() Author: Square Engineering Published: 2023-09-15T23:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [incident](), [Firewall](), [networking](), [datacenter](), [Microservice](), [systems]() Tags: [analysis](), [datacenters](), [engineering](), [firewall](), [incident](), [infrastructure](), [microservices](), [outage](), [root-cause-analysis](), [routing](), [systems]() ### AI overview Square describes a multi-hour outage beginning on September 7, 2023. The incident was caused by a host-based firewall change and a DNS service upgrade that together created unexpected load on internal DNS servers, leading services to lose communication with dependencies. The article provides a timeline, root-cause overview, and remediation steps. ### Source excerpt A timeline of the events of the outage and steps for remediation ## How trivago Maintains Global Availability During a Google Cloud Regional Outage DevFeed: [How trivago Maintains Global Availability During a Google Cloud Regional Outage]() Original publisher: [Read original article]() Author: Arne Claus Follow Published: 2022-08-15T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [Google Cloud Platform (GCP)](), [Kubernetes](), [Kafka](), [migration](), [Back end](), [sharding](), [Replication](), [systems](), [MySQL]() Tags: [backend](), [cloud](), [datacenters](), [failover](), [gke](), [google-cloud](), [how-to](), [kafka](), [migration](), [mysql](), [replication](), [sharding](), [systems]() ### AI overview This article explains trivago's regional failover testing and its effort to maintain global availability when a Google Cloud region becomes unavailable. It describes the move from locale-based sharding toward services that can handle equivalent traffic and data across regions. ### Source excerpt How trivago manages to stay globally available, even if a Google Cloud region goes down