News for hackers. Stuff that matters.
Re:We Saved $500k per Year by Rolling Our Own "S3" by codedokode on Sunday October 26, 2025 @09:54PM (#45716611)
And I am curious how many engineer years it requires to port code to cloud services and deal with multiple issues you cannot even debug due to not having root privileges in the cloud.

Without cloud, saving a file is as simple as "with open(...) as f: f.write(data)" + adding a record to DB. And no weird network issues to debug.

Re:We Saved $500k per Year by Rolling Our Own "S3" by rajamaka on Sunday October 26, 2025 @10:14PM (#45716726)
> as simple as "with open(...) as f: f.write(data)"

Save where? With what redundancy? With what access policies? With what backup strategy? With what network topology? With what storage equipment and file system and HVAC system and...

Without on-prem, saving a file is as simple as s3.put_object() !

Re:We Saved $500k per Year by Rolling Our Own "S3" by AdieuToLogic on Sunday October 26, 2025 @10:51PM (#45716939)
>> Without cloud, saving a file is as simple as "with open(...) as f: f.write(data)" + adding a record to DB.

> Save where? With what redundancy? With what access policies? With what backup strategy? With what network topology? With what storage equipment and file system and HVAC system and...

Most of these concerns can be addressed with ZFS[0] provided by FreeBSD systems hosted in triple-A data centers.

See also iSCSI[1].

0 - https://docs.freebsd.org/en/books/handbook/zfs/

1 - https://en.wikipedia.org/wiki/ISCSI

Re:We Saved $500k per Year by Rolling Our Own "S3" by SXX on Monday October 27, 2025 @02:16AM (#45717906)
Except running ZFS on FreeBSD would certainly require dedicated devops person with very specific skillset that majority of people on market dont have.
Re:We Saved $500k per Year by Rolling Our Own "S3" by codedokode on Sunday October 26, 2025 @10:20PM (#45716759)
With s3, you cannot use ls, grep and other tools.

> Save where? With what redundancy? With what access policies? With what backup strategy? With what network topology? With what storage equipment and file system and HVAC system and...

Wow that's a lot to learn before using s3... I wonder how much it costs in salaries.

> With what network topology?

You don't need to care about this when using SSDs/HDDs.

> With what access policies?

Whichever is defined in your code, no restrictions unlike in S3. No need to study complicated AWS documentation and navigate through multiple consoles (this also costs you salaries by the way). No risk of leaking files due to misconfigured cloud services.

> With what backup strategy?

Automatically backed up with rest of your server data, no need to spend time on this.

Re:We Saved $500k per Year by Rolling Our Own "S3" by rajamaka on Sunday October 26, 2025 @10:32PM (#45716840)
> You don't need to care about this when using SSDs/HDDs.

You do need to care when you move beyond a single server in a closet that runs your database, webserver and storage.

> No risk of leaking files due to misconfigured cloud services.

One misconfigured .htaccess file for example, could result in leaking files.

Re:We Saved $500k per Year by Rolling Our Own "S3" by codedokode on Monday October 27, 2025 @12:17AM (#45717338)
> One misconfigured .htaccess

First, I hope nobody is using Apache anymore, second, you typically store files outside of web directory.

Re:We Saved $500k per Year by Rolling Our Own "S3" by pestaa on Monday October 27, 2025 @04:12AM (#45718463)
Why nobody should use Apache? I rediscovered it to be great in many use cases. And there's llms to help with the config syntax.
Re:We Saved $500k per Year by Rolling Our Own "S3" by codedokode on Monday October 27, 2025 @04:27AM (#45718535)
Performance not great compared to nginx.
Re:We Saved $500k per Year by Rolling Our Own "S3" by AdieuToLogic on Sunday October 26, 2025 @11:59PM (#45717280)
>> No risk of leaking files due to misconfigured cloud services.

> One misconfigured .htaccess file for example, could result in leaking files.

I don't think you are making a compelling case here, since both scenarios result in an undesirable exposure. Unless your point is both cloud services and local file systems can be equally exploited?

Re:We Saved $500k per Year by Rolling Our Own "S3" by Nextgrid on Sunday October 26, 2025 @11:38PM (#45717194)
With bare-metal machines you can go very far before needing to scale beyond one machine.
Re:We Saved $500k per Year by Rolling Our Own "S3" by inlined on Sunday October 26, 2025 @10:37PM (#45716872)
It sounds like you’re not at the scale where cloud storage is obviously useful. By the time you definitely need S3/GCS you have problems making sure files are accessible everywhere. “Grep” is a ludicrous proposition against large blob stores
Re:We Saved $500k per Year by Rolling Our Own "S3" by coderintherye on Sunday October 26, 2025 @10:27PM (#45716803)
I mean you can easily mount the S3 bucket to the local filesystem (e.g. using s3fs-fuse) and then use standard command line tools such as ls and grep.
Re:We Saved $500k per Year by Rolling Our Own "S3" by hallman76 on Sunday October 26, 2025 @10:48PM (#45716926)
I inherited an S3 bucket where hundreds of thousands of files were written to the bucket root. Every filename was just a uuid. ls might work after waiting to page though to get every file. To grep you would need to download 5 TB.
Re:We Saved $500k per Year by Rolling Our Own "S3" by codedokode on Sunday October 26, 2025 @10:36PM (#45716861)
It's probably going to be dog slow. I dealt with HDDs where just iterating through all files and directories takes hours, and network storage is going to be even slower at this scale.
Re:We Saved $500k per Year by Rolling Our Own "S3" by Rohansi on Sunday October 26, 2025 @10:25PM (#45716785)
I don't think any of those mattered for their use case. That's why they didn't actually need S3.
Re:We Saved $500k per Year by Rolling Our Own "S3" by bcrosby95 on Sunday October 26, 2025 @10:21PM (#45716762)
You can't ever definitively answer most of those questions on someone else's cloud. You just take Amazons word for whatever number of nines they claim it has.
Re:We Saved $500k per Year by Rolling Our Own "S3" by rajamaka on Sunday October 26, 2025 @10:32PM (#45716842)
Not needing to ask the questions is the selling point.
Re:We Saved $500k per Year by Rolling Our Own "S3" by grebc on Sunday October 26, 2025 @11:37PM (#45717191)
Bro were you off grid last week. Your questions equally apply to AWS, you just magically handwave away all those questions as if AWS/GCP/Azure outages aren’t a thing.
Re:We Saved $500k per Year by Rolling Our Own "S3" by patrick451 on Sunday October 26, 2025 @11:44PM (#45717231)
Until it goes down because because aws STILL hasn't made themselves completely multi-region or can't figure our their DNS.
Re:We Saved $500k per Year by Rolling Our Own "S3" by beoberha on Sunday October 26, 2025 @11:47PM (#45717243)
A lot of reductive anti-cloud stuff gets posted here, but this might be the granddaddy of them all.
Re:We Saved $500k per Year by Rolling Our Own "S3" by mjr00 on Sunday October 26, 2025 @11:49PM (#45717250)
> Without cloud, saving a file is as simple as "with open(...) as f: f.write(data)" + adding a record to DB. And no weird network issues to debug.

There may be some additional features that S3 has over a direct filesystem write to a SSD in your closet. The people paying for cloud spend are paying for those features.

Re:We Saved $500k per Year by Rolling Our Own "S3" by RedShift1 on Sunday October 26, 2025 @11:01PM (#45716996)
Ah that is where logging and traceability comes in! But not to worry, the cloud has excellent tools for that! The fact that logging and tracing will become half your cloud cost, oh well let's just sweep that under the rug.
Re:We Saved $500k per Year by Rolling Our Own "S3" by hinkley on Sunday October 26, 2025 @10:25PM (#45716787)
Variation on an old classic.

Question: How do you save a small fortune in cloud savings?

Answer: First start with a large fortune.