If have a global user base, depending on your workload, a simple CDN in front of your hardware can often go a long ways with minimal cost and complexity.
> If have a global user base, depending on your workload, a simple CDN in front of your hardware can often go a long ways with minimal cost and complexity.
Let's squint hard enough to pretend a CDN does not qualify as "the cloud". That alone requires a lot of goodwill.
A CDN distributes read-only content. Any usecase that requires interacting with a service is automatically excluded.
> Any usecase that requires interacting with a service is automatically excluded
This isn't correct. Many applications consist of a mix of static and dynamic content. Even dynamic content is often cacheable for a time. All of this can be served by a CDN (using TTLs) which is a much simpler and more cost effective solution than multi-region cloud infra, with the same performance benefits.
As someone who spent 5 years attempting to get through zoning including a purely subjective “design review committee” in one of these affluent cities, I applaud this. While I agree with the desire to preserve the character and uniqueness one’s town, that pendulum has swung so far over driven by older, established nimbies who got theirs decades ago, or their offspring who inherited both homes and excessively low prop 13 tax rates locked in decades ago. The wealth disparity this whole system has created is staggering.
Sounds like an L1 or malfunctioning L2. I’d never revert to ICE in cold weather climates. Handling is great and ability to preheat (without idling) is a wonderful convenience on cold mornings.
+1 Bought a used X with FSD and learned the hard way to only use on freeways and highways in simple driving conditions or traffic. Even then I’m on constant alert for phantom braking. I can’t understand the $12,000 price justification.
I didn't mean scalability in terms of performance, but scalability in terms of maintenance effort. It's easy to SCP some files in, but the moment you want atomic deployments, it gets unnecessarily interesting.
PHP is the only language I've set up production environments for, but I can't see any reason why it would be more complicated than other languages.
I have a PHP project that handles atomic deployments by pointing the web server at a symlink named "latest". New versions get deployed into their own folder in the "versions" folder, and then the "latest" symlink gets pointed to the new version. Super simple to set up, and as long as you delete old versions as you go (keeping, say 3 versions so you can roll back as necessary) that's pretty much all there is to it. This all gets triggered by a Gitlab CI workflow, so I can hit a button to deploy after merging changes.
Another PHP-focused way to handle this would be deploying into a new folder, then updating the nginx config to point to that folder and running `service nginx restart`.
You can also use one of the many other atomic deployment options that replace more than just the running code, at which point the only difference between deploying a PHP webapp and deploying a Java/Go/Rust webapp is what gets included in your new server/container when you build it.
That's my entire point: the increase in complexity is very non-linear. With Python, Go, or whatever else, you pay a slightly higher upfront price, and you get things like atomic deployments out of the box; that price is however almost immediately amortised by the de-facto requirement to set up HTTPS/ACME, etc.
With PHP it's easier to just get started, but you've already mentioned versions, symlinks, CI, etc - that's the non-linear increase in complexity, you have to add a lot more pieces to get good ROI. With Python or Go you can continue using SCP to deploy for as long as it suits your needs, because no code changes will be picked up until you restart the process. If you need rollbacks, e.g. Go doesn't need symlinks or versioned directories - the entire app is a single executable, so you can just keep copies of these. You pay for what you use, and the returns are more linear and immediate.
If you only have experience deploying PHP, I would sincerely recommend trying other languages/runtimes/frameworks, even if for no other reason than to learn from what the rest of the world is doing. For me, learning to deploy PHP correctly was also a horizon-broadening experience.
+1 for iCloud+. I moved 3 business/family domains and shutdown my G Suite legacy account with no issues, and no extra cost (already paying for iCloud). Can't beat $0.99/mo for 50GB shared on up to 6 accounts.
+1 for iCloud+. I got the 200 to give my cousin a way to backup her pictures (around 30 GB, and it annoyed me she wasn't backing them up) The custom domain was nice, and I moved all of them to iCloud+.
iCloud / OneDrive / Google Drive / DropBox are not a backup solution despite the vendors promoting it.
They are there only for convenience.
I have experienced file loss on OneDrive. I am now using iCloud and have had no file loss whatsoever. I regularly diff my offline backup with iCloud Drive contents mirrored to my mac.
Also to note: About 50% of the stories you hear are users being morons. My sister lost some files. She deleted them after fat fingering something and blamed the cloud vendor (Google). It happens.
Make sure you back up stuff separately and fully offline. You’re just as fucked if someone rips off your account.
> Also to note: About 50% of the stories you hear are users being morons. My sister lost some files. She deleted them after fat fingering something
Some of these services (e.g. Dropbox) have rollback which would have helped in this situation, and most have a "Rubbish Bin" you can undelete from. I often click on the wrong thing because the web UI is lagging and I delete something by mistake.
I agree these services right now are all for convenience. There are horror stories from all of them, except for rsync (who are active on here) - I've never heard of any horror stories from their cloud service, but obviously if your payment stops for whatever reason, then all your stuff is gone with any of these.
I got a 15 GB account with Mega. I activated a bonus and got about 5 more. It's full now, but I forgot about that fact until I got an email about that I need to upgrade—bonus has expired —, or they're going to delete the data. But until I do, I can't delete the data, I can't do anything except pay, or everything's gone. So, I guess everything's gone. There is no way I'm putting my card on a service that kidnaps data.
AFAIK 20GB is now free forever for active accounts, so that email might just be a reminder to log in to refresh it.
If not, you can also subscribe via Google Play or the App Store and keep your payment info safe that way. (I didn't sign in to check if they support PayPal or the like)
If I ever will experience a file loss on iCloud I think I won’t even ever know the way it’s designed and the way it’s documented and the way way Apple deals with it even after reporting an issue.
Unless you deploy another tool or service to keep checking whether everything has been a file loss or inconsistency inside iCloud. Yes, it’s that opaque!
On the contrary on Dropbox I know exactly what is going on and there are features to revert a change.
If something happens with your iCloud and you get really locked out, is there good support to get you back in?
With Gmail, there is basically no human support these days.
I just had a buddy come to me after someone tried to brute force his sbcglobal email and locked him out; AT&T have told him it might take someone up to 2 months to get to his support request.
+1 for Fastmail. I've used them for almost 20 years and their support has been great.
