Disclosure: I work on Google Cloud. Apologies if you find this to be in poor taste, but GCS directly supports the S3 XML API (including v4): https://cloud.google.com/storage/docs/interoperability and has easy to use multi-regional support at a fraction of the cost of what it would take on AWS. I directly point my NAS box at home to GCS instead of S3 (sadly having to modify the little PHP client code to point it to st…
I keep telling people that in my view, Google Cloud is far superior to AWS from a technical standpoint. Most people don't believe me... Yet. I guess it will change soon.
Disclosure: I work on Google Cloud. Apologies if you find this to be in poor taste, but GCS directly supports the S3 XML API (including v4): https://cloud.google.com/storage/docs/interoperability and has easy to use multi-regional support at a fraction of the cost of what it would take on AWS. I directly point my NAS box at home to GCS instead of S3 (sadly having to modify the little PHP client code to point it to st…
We would definitely seriously consider switching to GCS more if your cloud functions were as powerful as AWS Lambda (trigger from an S3 event) and supported Python 3.6 with serious control over the environment.
S3 is currently (22:00 UTC) back up. The timeline, as observed by Tarsnap: First InternalError response from S3: 17:37:29 Last successful request: 17:37:32 S3 switches from 100% InternalError responses to 503 responses: 17:37:56 S3 switches from 503 responses back to InternalError responses: 20:34:36 First successful request: 20:35:50 Most GET requests succeeding: ~21:03 Most PUT requests succeeding: ~21:52
no. soundcloud uses aws s3. it is still down. this is false information.
I use a master and four mirror slaves. Then use round robin for reads. I used to have three slaves, but when two of them was down at the same time I got nervous and set up one more.
How does that work with S3? Your master and slaves are presumably just SQL databases, right? Or?
vps via different providers. think RAID but with VPS.
S3 is currently (22:00 UTC) back up. The timeline, as observed by Tarsnap: First InternalError response from S3: 17:37:29 Last successful request: 17:37:32 S3 switches from 100% InternalError responses to 503 responses: 17:37:56 S3 switches from 503 responses back to InternalError responses: 20:34:36 First successful request: 20:35:50 Most GET requests succeeding: ~21:03 Most PUT requests succeeding: ~21:52
no. soundcloud uses aws s3. it is still down. this is false information.
"[RESOLVED] Increased Error Rates
Update at 2:08 PM PST: As of 1:49 PM PST, we are fully recovered for operations for adding new objects in S3, which was our last operation showing a high error rate. The Amazon S3 service is operating normally."
S3 is currently (22:00 UTC) back up. The timeline, as observed by Tarsnap: First InternalError response from S3: 17:37:29 Last successful request: 17:37:32 S3 switches from 100% InternalError responses to 503 responses: 17:37:56 S3 switches from 503 responses back to InternalError responses: 20:34:36 First successful request: 20:35:50 Most GET requests succeeding: ~21:03 Most PUT requests succeeding: ~21:52
no. soundcloud uses aws s3. it is still down. this is false information.
Soundcloud recovering from this failure and S3 being operational are two separate issues. We use S3 and it will take us nominally an hour to recover after S3 went up, for example.
S3 has started working as of about 20 minutes ago, and things are running smoothly.
no. soundcloud uses aws s3. it is still down. this is false information.
"[RESOLVED] Increased Error Rates Update at 2:08 PM PST: As of 1:49 PM PST, we are fully recovered for operations for adding new objects in S3, which was our last operation showing a high error rate. The Amazon S3 service is operating normally." https://status.aws.amazon.com/
oh the famous downvote for the smear campaign. just admit it.
Disclosure: I work on Google Cloud. Apologies if you find this to be in poor taste, but GCS directly supports the S3 XML API (including v4): https://cloud.google.com/storage/docs/interoperability and has easy to use multi-regional support at a fraction of the cost of what it would take on AWS. I directly point my NAS box at home to GCS instead of S3 (sadly having to modify the little PHP client code to point it to st…
I've used both Google Cloud and AWS, and as of a year or so ago, I'm a Google Cloud convert. (Before that, you guys didn't at all have your shit together when it came to customer support) It's not in bad taste, despite other comments saying otherwise. We need to recognize that competition is good, and Amazon isn't the answer to everything.
Me too. We switched to Google Cloud years ago at its inception and have never looked back -- always viewed it as a competitive advantage due to its solid, more advanced infrastructure -- faster network, reliable disks, cleaner UI that's easier to manage. Just a cleaner operation all the way around.
Disclosure: I work on Google Cloud. Apologies if you find this to be in poor taste, but GCS directly supports the S3 XML API (including v4): https://cloud.google.com/storage/docs/interoperability and has easy to use multi-regional support at a fraction of the cost of what it would take on AWS. I directly point my NAS box at home to GCS instead of S3 (sadly having to modify the little PHP client code to point it to st…
We would definitely seriously consider switching to GCS more if your cloud functions were as powerful as AWS Lambda (trigger from an S3 event) and supported Python 3.6 with serious control over the environment.
Disclosure: I work on Google Cloud. Apologies if you find this to be in poor taste, but GCS directly supports the S3 XML API (including v4): https://cloud.google.com/storage/docs/interoperability and has easy to use multi-regional support at a fraction of the cost of what it would take on AWS. I directly point my NAS box at home to GCS instead of S3 (sadly having to modify the little PHP client code to point it to st…
We would definitely seriously consider switching to GCS more if your cloud functions were as powerful as AWS Lambda (trigger from an S3 event) and supported Python 3.6 with serious control over the environment.
Is there something about the GCS trigger that doesn't work for you? I hear you on Python 3, but I'm also curious about "serious control over the environment". Can you be more specific?