Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

223
active users

veganism.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-alpha.4

#database

32 posts28 participants0 posts today
Public *
Curated Hacker News

Beyond Performance: Measuring the environmental impact of analytical databases

arxiv.org/abs/2504.18980

arXiv logo
arXiv.orgBeyond Performance: Measuring the Environmental Impact of Analytical DatabasesThe exponential growth of data is making query processing increasingly critical for modern computing infrastructure, yet the environmental impact of database operations remains poorly understood and largely overlooked. This paper presents ATLAS, a comprehensive methodology for measuring and quantifying the environmental footprint of analytical database systems, considering both operational impacts and manufacturing costs of hardware components. Through extensive empirical evaluation of four distinct database architectures (DuckDB, MonetDB, Hyper, and StarRocks), we uncover how fundamental architectural decisions affect environmental efficiency. Our findings reveal that environmental considerations in database operations are multifaceted, encompassing both immediate operational impacts and long-term sustainability implications. We demonstrate that architectural choices can significantly influence both power consumption and environmental sustainability, while deployment location emerges as a critical factor that can amplify or diminish these architectural advantages.
#arxiv#database
Public
Paul Chambers🚧

Oracle engineers caused 5 days-long software outages at (at least) 45 U.S. hospitals after engineers conducting maintenance work mistakenly deleted critical storage connected to a key #database causing the facilities to temporarily return to paper-based patient systems. #data #oracle

cnbc.com/2025/04/28/oracle-eng

CNBCOracle engineers caused days-long software outage at U.S. hospitalsOracle engineers triggered a five-day outage at several Community Health Systems hospitals, causing the facilities to temporarily return to paper-based records.
Public
N-gated Hacker News

🎉 Ah yes, the cutting-edge #innovation of yet another #database solution that promises to do everything but make your coffee ☕. Attend our #virtual #meetup to discuss how one magical tool can handle both #metrics and #logs, because who doesn't love a good fantasy story? 😂✨
greptime.com/blogs/2025-04-24- #techhumor #HackerNews #ngated

greptime.comBeyond ELK: Lightweight and Scalable Cloud-Native Log MonitoringThis article explores the growing limitations of the ELK stack in modern log storage scenarios and introduces GreptimeDB as a next-generation log database with advantages in both architecture and user experience. By combining Vector with GreptimeDB, we demonstrate a complete pipeline—from log collection and storage to parsing and querying.
Public
Curated Hacker News

Shardines: SQLite3 Database-per-Tenant with ActiveRecord

blog.julik.nl/2025/04/a-can-of

Julik Tarkhanov · A Can of Shardines: SQLite Multitenancy With RailsThere is a pattern I am very fond of - “one database per tenant” in web applications with multiple, isolated users. Recently, I needed to fix an application I had for a long time where this database-per-tenant multitenancy utterly broke down, because I was doing connection management wrong. Which begat the question: how do you even approach doing it right? And it turns out I was not alone in this. The most popular gem for multitenancy - Apartment - which I have even used in my failed startup back in the day - has the issue too. The culprit of does not handle multithreading very well is actually deeper. Way deeper. Doing runtime-defined multiple databases with Rails has only recently become less haphazard, and there are no tools either via gems or built-in that facilitate these flows. It has also accrued a ton of complexity, and also changes with every major Rails revision. TL;DR If you need to do database-per-tenant multitenancy with Rails or ActiveRecord right now - grab the middleware from this gist and move on. If you are curious about the genesis of this solution, strap in - we are going on a tour of a sizeable problem, and of an API of stature - the ActiveRecord connection management. Read on and join me on the ride! Many thanks to Kir Shatrov and Stephen Margheim for their help in this.
#database
Public *
Jack C.

Finally came up with a project to learn #Rust with. Not moving particularly fast, but it's making me spend a lot of time considering the implementation of data structures with ownership and lifetimes in mind.

I've been away from system-level programming for a while and last time I did any it was #C++ which is its own kind of pain.

Working on building up structures backed by a #sqlite #database as well, so getting #SQL practice also.

#RustLang#CPlusPlus#CPP
Continued thread
Public
Nonilex

The #FBI has its own “Next Generation Identification” #biometric & #criminal-history #database program; the agency also has a #FacialRecognition apparatus capable of matching people against >640M photos—a database made up of #DriversLicense & #passport photos, as well as mug shots. The #SocialSecurity Admin keeps a master #earnings file, which contains the “individual earnings histories for each of the 350+ million SSNs that have been assigned to workers.”

#Trump#law#privacy
Public
Curated Hacker News

Shardines: SQLite3 Database-per-Tenant with ActiveRecord

blog.julik.nl/2025/04/a-can-of

Julik Tarkhanov · A Can of Shardines: SQLite Multitenancy With RailsThere is a pattern I am very fond of - “one database per tenant” in web applications with multiple, isolated users. Recently, I needed to fix an application I had for a long time where this database-per-tenant multitenancy utterly broke down, because I was doing connection management wrong. Which begat the question: how do you even approach doing it right? And it turns out I was not alone in this. The most popular gem for multitenancy - Apartment - which I have even used in my failed startup back in the day - has the issue too. The culprit of does not handle multithreading very well is actually deeper. Way deeper. Doing runtime-defined multiple databases with Rails has only recently become less haphazard, and there are no tools either via gems or built-in that facilitate these flows. It has also accrued a ton of complexity, and also changes with every major Rails revision. TL;DR If you need to do database-per-tenant multitenancy with Rails or ActiveRecord right now - grab the middleware from this gist and move on. If you are curious about the genesis of this solution, strap in - we are going on a tour of a sizeable problem, and of an API of stature - the ActiveRecord connection management. Read on and join me on the ride! Many thanks to Kir Shatrov and Stephen Margheim for their help in this.
#database
VegansExploreLive feeds
About