News for hackers. Stuff that matters.
Re:In praise of S3 by ktpsns on Tuesday March 24, 2020 @10:28AM (#22674949)
As a devloper, I have never used S3, despite, of course, heard thousands of times of it. I'm kind of traditional: "Cloud" still means "just another person's hard drive", and "serverless" means "just another person's computer" for me. Having a feel for privacy, I still run a NAS at home, and it's terrible: I really appreciate the amount of work put into S3. Somehow, as a developer, I was able to avoid all that fancy cloud stuff. I prefer self-hosted, but I'm bad at finding good arguments which support my point nowadays :-/
Re:In praise of S3 by dividuum on Tuesday March 24, 2020 @10:51AM (#22675093)
> "just another person's hard drive"

In general I'm with you, but that here is the main benefit imho. I don't have the nerves to operate my own redundant, transparently growing and reliable storage system for my business. For use cases where privacy is important (like backups, private user data, etc), encrypting data before uploading limits the privacy leaks to metadata which might be acceptable.

Re:In praise of S3 by vorpalhex on Tuesday March 24, 2020 @11:35AM (#22675435)
The tools for doing this at "medium business" and below scale have gotten much easier, especially with things like ZFS.
Re:In praise of S3 by hjanssen on Tuesday March 24, 2020 @01:06PM (#22676402)
which is still orders of magnitude harder than create an account and pay a bill
Re:In praise of S3 by Spivak on Tuesday March 24, 2020 @11:12AM (#22675230)
AWS is impressive because they're running everyone's scalable reliable redundant storage server. It's not so scary when you just have to do it for your own small pond.
Re:In praise of S3 by jnbiche on Tuesday March 24, 2020 @11:27AM (#22675370)
But you have to build the same level of redundancy and reliability for your small pond if you want to achieve S3's uptime. Scaling is the hardest part, but it's just one part of the puzzle.
Re:In praise of S3 by anderspitman on Tuesday March 24, 2020 @11:41AM (#22675494)
Do you really need more than basic redundancy + backups? I think most small businesses would survive a few hours restoring backups every few years.
Re:In praise of S3 by NikolaeVarius on Tuesday March 24, 2020 @12:17PM (#22675868)
This assumes backups work.
Re:In praise of S3 by rsync on Tuesday March 24, 2020 @12:11PM (#22675793)
"Somehow, as a developer, I was able to avoid all that fancy cloud stuff."

I am genuinely interested in what you think about things like this:

    ssh [email protected] du -Ahd2 some/directory

    pg_dump -U postgres db | ssh [email protected] "dd of=db_dump"
or maybe even:

    ssh [email protected] "git clone git://github.com/freebsd/freebsd.git freebsd"
Setting aside these "rsync.net tricks", I think you should look into the 'borg'[1][2] backup tool. It has become the de facto standard for remote backups because it does everything that rsync does (efficient, changes only backups) but also produces strongly encrypted remote backup sets that only you have a key to ...

[1] https://borgbackup.readthedocs.io/en/stable/

[2] https://www.stavros.io/posts/holy-grail-backups/

Re:In praise of S3 by dvfjsdhgfv on Tuesday March 24, 2020 @10:51AM (#22675091)
S3 in itself is tangential to privacy abuses; you can (and probably should) use it to store encrypted data only, if it's the kind of data you'd prefer not to be accessed by someone else. But most people don't use it with encryption as it's less convenient.

The real argument against S3 though is its price. For any but most trivial amounts of data it's terribly expensive and I use it only as internal storage for other AWS services.

Re:In praise of S3 by bradleyankrom on Tuesday March 24, 2020 @11:07AM (#22675197)
I’ve found the overall price to be quite reasonable. We have about 10TB stored across maybe 40M objects - the biggest cost is for PUTs, but even those requests + storage keeps the bill around $150US. At the enterprise level, that’s a negligible cost. YMMV, of course.
Re:In praise of S3 by dvfjsdhgfv on Tuesday March 24, 2020 @11:40AM (#22675477)
For these kinds of amounts you could use the cheapest of Hetzner SX line and save half of that. But real savings start over 100 TB.
Re:In praise of S3 by pnutjam on Tuesday March 24, 2020 @11:55AM (#22675633)
Especially when you want to get the data out, B3 (from backblaze) has a much better cost structure.
Re:In praise of S3 by ignoramous on Tuesday March 24, 2020 @10:32AM (#22674972)
> I still run a NAS at home, and it's terrible... I prefer self-hosted...

One could self-host minio which is nice S3 replacement: https://github.com/minio/minio

Re:In praise of S3 by K0SM0S on Tuesday March 24, 2020 @11:35AM (#22675439)
Would you consider bootstrapping a small / freelancing business using this?

(Assuming an already enterprise-y prosumer IS, i.e. pfSense, VLANs, ZFS storage, 'enough' CPU/RAM/network, all patched and well in good sysadmin fashion, inet-facing resources behind some reverse proxy, etc).

Re:In praise of S3 by klohto on Tuesday March 24, 2020 @11:47AM (#22675550)
Who’s your target? You can do all of these with AWS already and much cheaper. On top of that, getting all the necessary certifications that AWS has will take you a year and huge sum of money.
Re:In praise of S3 by K0SM0S on Tuesday March 24, 2020 @11:07PM (#22681625)
In short,

The first target is internal customers for a consulting dev shop — i.e. me + n first partners / founders / employees (I'll begin alone but with a goal to grow to ~3 people asap).

So website, storage w. inet-facing endpoints, security all the way (encrypt etc), and basic IT stuff for dev: e.g. private GitLab + straightforward CI/CD pipe. I figure all developers need is an endpoint to push git, and access to the automation processes.

____

Longer elaboration, FWIW (maybe not much to answer the question but I'm a bit over my head on this topic so I'd rather share too much, to get debunked where needed).

The rationale to bootstrap as self-hosted is simply that it's already paid (gear is humming as I write) and I'm “99% sure I can guarantee 99% uptime” (the full setup is split in two homes 500km apart, each behind 1Gbps symmetrical business-grade fiber, each site being in High-Availability locally— from router/firewalls to storage passing by proxies and k8s-pods).

Re certs, well in a bootstrap scenario we'd worry about those later I suppose, when there's actual demand to justify the overhead cost (first clients are likely to be extremely low-profile, looking for a "break" too). Legally, clients own their code and infra at the end of the day, we would deliver a product/tool but not host it (not an MSP; we'd typically rather work with their MSP— or recommend one —to smooth out their operation, add critical value to key pain points).

In terms of actual workloads, I'm looking at custom domain-parametized ML/DL services (think: selling very specialized neural nets that solve one problem extremely well for this one company, e.g. classifying internal docs). So I need some in-house hardware anyway to experiment when developing models (it's painful and limiting to be forced to spend at the exploratory stage, for each project).

I figure my first partners or employees would either run their stuff locally or tap into my GPUs; we'd likely pay for the big guns on AWS or GC only for actual prod training iterations (those that earn us actual money when our work is 'good enough', final drafts so to speak).

It's a bit of a maverick project¹, hoping to leverage ML in profitable ways for small operations (obviously as we accumulate clients and experience, we'd get better at nailing areas of best-value optimization). It will be a rocky road during the early phase (first two years at least). The costs can skyrocket pretty fast with ML on clouds, I'm extremely wary of such fuckups, not to mention running the ongoing risk of being cancelled or shutdown (account terminated or frozen) for whatever reasons — so better have "plan B"... which historically might have begun as plan A, i.e. self-hosting.

I've also got a long-term angle of building expertise, so I've a positive bias for on-prems: if this thing works and grows enough, we'll definitely look at running the operation in-house, because clouds cost proposition for ML is too steep to scale profitably if it's your core business, or so I hear (and before one says "but Spotify is on whatever cloud", yeah, that's not their core business, they don't sell AI but music; we're the guys who sell AI to Spotify ideally). So, in ML for now, gotta get'em GPUs and TPUs to make a mark. Thus I'd rather learn all of it (myself maybe, as a company surely) sooner rather than later. It's gonna come down to this anyway, if this maverick thing works.

1: "maverick" as of 2020, but I suspect there will be a whole market of such consulting / ML shops by 2030.

Re:In praise of S3 by jacurtis on Tuesday March 24, 2020 @11:21AM (#22675316)
I can see your point if you think about S3 as a replacement to an at-home NAS. For that comparison, S3 is not at all competitive. Price alone is $23/Tb/mo, if you are replacing 4Tb on a NAS, you would be paying ~$100/mo before you even consider egress fees (paying to download). It is less convenient than a NAS, and you have the potential privacy concerns. I total agree that S3 is a terrible NAS replacement.

However, S3 isn't trying to replace your NAS. S3 offers many use cases where it is the smartest and most viable solution. The most common use case is as centralized block storage for an online web app, that runs on load balancers, a CDN, and distributed servers. If you run an app that is going to run on multiple servers and get load balanced between them, then uploading directly to the servers is complicated. Since a user could upload something to server A one time, and a month later they could request the file while visiting on server B, C, D, E, etc. This centralized S3 platform simplifies the block storage for these large apps.

S3 does offer more advanced features as well that many people aren't educated on. For example, S3 Lifecycle Management allows you to set up timelines so that your file uploads are available on S3 for 30 days (when users are most likely to access them), then automatically move them to reduced redundancy (reduces cost, but at lower 99.9% SLA) when the file is 30-120 days old, and after that it moves to Glacier storage (long term, taped storage, super cheap), for long term storage when it is unlikely to be retrieved but needs to be kept. You can also set up a CDN just for this block storage, with over 200 edge locations all around the world.

S3 also offers HIPAA and PCI compliance. There is also incredibly robust user management (Through AWS IAM). Plus you get 11x9's of availability (99.999999999% availability).

Im not trying to sell you on S3. It definetely isn't for everyone. There are times when I would tell people that it isn't a good fit. But if you work on enterprise apps, it gives you a lot of enterprise level features for month-to-month, (relatively) straightforward pricing, no long term commitements, etc. Which is something that doesn't generally exist in the world of enterprise software or PAAS (which is what S3 really is). So for that, S3 is a breakthrough product.

S3's biggest flaw is its price. If you are using all the enterprise features than it is arguably worth it, especially considering the 11 nines of availability. But for anyone on a non-enterprise app that doesn't need that stuff, there are far cheaper solutions out there for you. Blackblaze B2, Wasabi, Digital Ocean Spaces are three that come to mind.

Re:In praise of S3 by jscholes on Tuesday March 24, 2020 @11:29AM (#22675384)
> Blackblaze B2, Wasabi, Digital Ocean Spaces are three that come to mind.

Seconded on the last two in this list. I use both, for completely personal storage needs. I was lucky enough to get Wasabi's older, cheaper pricing model for the lifetime of my account, but even so it's a hugely attractive option for storing large amounts of data without worrying about local equipment and all the rest of it.

Re:In praise of S3 by ignoramous on Tuesday March 24, 2020 @01:18PM (#22676520)
> I was lucky enough to get Wasabi's older, cheaper pricing model for the lifetime of my account

You'd like https://scaleway.com free-tier of 75GB object storage / transfers per month.

Re:In praise of S3 by jscholes on Tuesday March 24, 2020 @01:36PM (#22676677)
Thanks for the heads-up, looks great and is S3-compatible too.
Re:In praise of S3 by anderspitman on Tuesday March 24, 2020 @11:44AM (#22675523)
And I'll second the first. B2 has been a great experience for me.
Re:In praise of S3 by matwood on Tuesday March 24, 2020 @12:28PM (#22675991)
Same. I use B2 as a backup location for Arq, and it's inexpensive and has worked great.
Re:In praise of S3 by sfg75 on Tuesday March 24, 2020 @12:55PM (#22676270)
> Plus you get 11x9's of availability (99.999999999% availability).

Note that those 9s are for durability

From https://aws.amazon.com/s3/faqs/#How_durable_is_Amazon_S3:

"This durability level corresponds to an average annual expected loss of 0.000000001% of objects. For example, if you store 10,000,000 objects with Amazon S3, you can on average expect to incur a loss of a single object once every 10,000 years"

Re:In praise of S3 by vorpalhex on Tuesday March 24, 2020 @11:33AM (#22675418)
For what it's worth, you can get "S3 compatible" solutions for your local/colo'd hardware through Ceph or Minio - and I use S3 on my homeserver because it's such a robust and well supported protocol in a lot of apps that don't support ssh/syncthing.
Re:In praise of S3 by tmh88j on Tuesday March 24, 2020 @11:09AM (#22675210)
>I'm kind of traditional: "Cloud" still means "just another person's hard drive", and "serverless" means "just another person's computer" for me.

I agree for the most part on cloud, but isn't "another person's computer" just a server? Serverless is more like a service running on a server that requires zero configuration or maintenance for you, just add your code and it works. Typically that means no messing with apache, nginx, no language nor framework setup/configuration, etc...

Re:In praise of S3 by MonaroVXR on Tuesday March 24, 2020 @12:46PM (#22676172)
> Serverless is more like a service running on a server that requires zero configuration or maintenance for you, just add your code and it works. Typically that means no messing with apache, nginx, no language nor framework setup/configuration, etc...

Whoa, I thought it was: Use a server, use a CDN, shutdown the server and its running serverless. Because everything is getting hitting the CDN and not the actual server.

Re:In praise of S3 by tmh88j on Tuesday March 24, 2020 @02:28PM (#22677364)
I'm not sure what purpose of the server is at the start in that example, but sure, that's a common serverless architecture. S3 has an option to host static websites. You can upload HTML/JS to an S3 bucket and it will serve the content. Unless the site is truly static, the JS will be making requests to other servers/services/APIs.

Obviously it's on a server, but the "serverless" part comes from not having to provision and manage a server. You can put your code a a service and allow those services (S3, Lambda, API Gateway, etc...) to do the "server" work for you.

Serverless is kind of a generic term. I guess hosting sites like GoDaddy that allow you drag and drop some PHP, HTML and JS files into a CPanel type interface are technically serverless, since you're not managing a server. Put some code up there and let their platform run it for you.

Re:In praise of S3 by MonaroVXR on Tuesday March 24, 2020 @07:10PM (#22680054)
I genuinely don't understand this. You can use Jenkins with Kubernetes or Openshift to do this right?
Re:In praise of S3 by tmh88j on Wednesday March 25, 2020 @12:24AM (#22681928)
Serverless is just a buzzword for a service that you'd typically have to operate your own server for, but the service completely removes the need for that so you can focus solely on that (usually) one task. It also goes hand in hand with microservices, you'll see those two used together a lot because microserves are often built using serverless services. You can make it as complex or as simple as you like. Your entire application doesn't have to be serverless, you can have even just a single small piece of it running serverless.

For example, going back to a serverless frontend using S3 that I mentioned before. You can host a JavaScript SPA on S3 and use a service like Route 53 for DNS. Your JavaScript can then make API calls to a full-on server that you manage, say an EC2 instance with a LAMP stack or even Azure with C#/.NET. Your front end is serverless because it's just hosted on S3 and you're not maintaining a server, but your backend code would be deployed and served however you like, such as Jenkins and Kubernetes like you mentioned.

AWS lambda is a good intro to the world of serverless computing if you're not familiar with it. While you can write code on your computer and use the AWS CLI to upload it, the AWS console even has a text editor that resembles JS Fiddle. It can receive events from other AWS services and you can write JavaScript, Python, Java, Ruby, C#, Go and PowerShell to process those events and do whatever you like, such as writing a DB record or adding something to an SQS queue. The point is you're writing real production code that does not live on a server you manage.

Re:In praise of S3 by jbverschoor on Tuesday March 24, 2020 @11:14AM (#22675242)
Simply moving that towards the developer who must adhere to the available "serverless" servers + configurationscreens. J2EE re-invented.
Re:In praise of S3 by tmh88j on Tuesday March 24, 2020 @11:16AM (#22675265)
I don't understand, are you disagreeing with what I've said or just saying we've had the concept of serverless for a while?
Re:In praise of S3 by viridian on Tuesday March 24, 2020 @01:22PM (#22676552)
I don't see how you equate serverless with another person's computer. Cloud computing is another person's computer, sure, but there's not really a local equivalent for something like AWS Lambda as far as I know. Having an API call or trigger that pops a machine into existence, runs the code, and terminates the machine in a couple hundred milliseconds isn't something I've ever really seen used outside of clouds environments.