Hacker News new | past | comments | ask | show | jobs | submit login

Stuff like this is always possible wherever you have fully centralized architecture. I don't know how many massive cloud failures it will take for IT community at large to realize this.



Salesforce launched in 1999 before before cloud was a thing. It's basically just a big Oracle database.


That's not very fair to a company that was one of the pioneers of a lot of the things we consider normal on today's software as a service.

Also incorrect, they have great cloud and devops practices. If anything it's likely this bug's impact would be limited due to how decentralised SFDC operates.

Still a massive fuck-up, I'm interested in seeing if they'll release any more detail on why it happened.


While a little unfair, and Salesforce is a decent product with nice dev tooling (apart from the weird ancient Java ish custom language), but under the hood, it really is just a Oracle database per org.


Weird ancient proprietary language.

Impossible to run locally.

No debuggers.

Virtually impossible to put an entire org in source control.

No package manager.

More undefined behavior than a C compiler.


> decent product with nice dev tooling

whaaaaaaaaaaaaaaaaat hahahaha i can't take that seriously; I've used it and it felt like a giant pit of despair


Well,

they do own heroku

https://www.heroku.com/


They purchased Heroku.


In fairness they did do long enough ago that they would have massively messed it up if they at least didn't understand something about running software.

SFDC hate is pretty common, maybe because of how big they are. I think that their tech is actually pretty impressive.


The hate is likely propelled in part because their sales process is the work of Satan.

Like seriously I would rather lick alcohol soaked razor blades than do a standard annual renewal of a Salesforce contract.


Other than being pretty public at this point, this incident could have easily happened in an upgrade/rollout in on-premise settings as well (at least without a good staging environment and test process).


You get all kinds of new and exciting failure and fuck up modes in a decentralized architecture.


If I add a service listening on port 1234 that pipes text input to a root terminal most likely no one will ever know.

That's the advantage of decentralized architecture. It's a disadvantage too though ...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: