Live data from Hacker News

The 2002 mandate for internal communication systems at Amazon

sametab.com

51–60 of 187 posts

Re: The 2002 mandate for internal communication systems at Amazon

#51
post #43
post #40

> While the third point makes all the difference in the world, what Amazon really did get right that Google didn’t was an internal communication system designed to make all the rest possible. > Having teams acting like individual APIs and interacting with one another through interfaces over the network was the catalyst of a series of consequent actions that eventually made possible the realization of AWS in a way tha…

> Google has worked this way since time immemorial. Do internal Google services exclusively use the Google Cloud Platform APIs? The implication is that internal Amazon services exclusively use AWS APIs. I've never worked at either company though, so I don't know if it's true. Perhaps someone could clarify.

> The implication is that internal Amazon services exclusively use AWS APIs.

Untrue. Some even use older version of AWS "core" services (S3), not the latest and greatest version of AWS services.

Re: The 2002 mandate for internal communication systems at Amazon

#52

> 6) Anyone who doesn’t do this will be fired. So I've never worked at a company over 150 people. Is this... a normal thing for an email? Maybe I'm just one of those softies but an email with that line would throw me off my day and cause a serious hit to my morale and confidence of working there.

Your parent comment kind of ripped that one out of context by omitting the following statement that is supposed to contrast with the preceding statement in a humorous way (IMHO).

    6) Anyone who doesn’t do this will be fired.
    7) Thank you; have a nice day!
This makes it sound like hyperbole instead, or a quip used to essentially communicate "It's very high priority".

Re: The 2002 mandate for internal communication systems at Amazon

#53
post #33

Earlier quoted context omitted.

This is one of the niches where (S)FTP and batch processing is still alive and kicking.

Yeah, SFTP + CSV file is still the standard for enterprise software. The problem is that these kinds of things have to be built to the lowest common denominator, which is usually the customer anyway. The customer in enterprise software is usually not a tech company they typically have outdated IT policies and less skilled developers than a pure tech company would have. Even if the developers are capable of doing some…

[deleted]

Re: The 2002 mandate for internal communication systems at Amazon

#55
post #43

Earlier quoted context omitted.

> Google has worked this way since time immemorial. Do internal Google services exclusively use the Google Cloud Platform APIs? The implication is that internal Amazon services exclusively use AWS APIs. I've never worked at either company though, so I don't know if it's true. Perhaps someone could clarify.

> The implication is that internal Amazon services exclusively use AWS APIs. Untrue. Some even use older version of AWS "core" services (S3), not the latest and greatest version of AWS services.

though in some cases I can think of, the "legacy" service is now just a facade over an AWS service.

Re: The 2002 mandate for internal communication systems at Amazon

#56
post #43
post #40

> While the third point makes all the difference in the world, what Amazon really did get right that Google didn’t was an internal communication system designed to make all the rest possible. > Having teams acting like individual APIs and interacting with one another through interfaces over the network was the catalyst of a series of consequent actions that eventually made possible the realization of AWS in a way tha…

> Google has worked this way since time immemorial. Do internal Google services exclusively use the Google Cloud Platform APIs? The implication is that internal Amazon services exclusively use AWS APIs. I've never worked at either company though, so I don't know if it's true. Perhaps someone could clarify.

No, because internal APIs for the same backends are more powerful and easier to integrate with. It's not easy to make the external APIs as useful and powerful as internal ones: for one, you can trust your users more to do the right thing and not try to exploit you for profit, it's much less committment to offer certain functionalities, since it's easier to roll them back if only users are internal, etc. Google is slowly getting there in feature parity, but so much effort has been invested in Google internal ecosystem even before GCP has even existed that, as good as GCP is, nobody wants to bet on it when obviously superior alternative is available.

Re: The 2002 mandate for internal communication systems at Amazon

#57
> what Amazon really did get right that Google didn’t was an internal communication system designed to make all the rest possible.

I'm not following what he means. What is the thing he is describing as "an internal communication system" here? That made all the rest possible? What is/was this internal communications system?

Re: The 2002 mandate for internal communication systems at Amazon

#58

> what Amazon really did get right that Google didn’t was an internal communication system designed to make all the rest possible. I'm not following what he means. What is the thing he is describing as "an internal communication system" here? That made all the rest possible? What is/was this internal communications system?

I'm assuming Yegge was referring to the RPC framework.

Re: The 2002 mandate for internal communication systems at Amazon

#59

> 6) Anyone who doesn’t do this will be fired. So I've never worked at a company over 150 people. Is this... a normal thing for an email? Maybe I'm just one of those softies but an email with that line would throw me off my day and cause a serious hit to my morale and confidence of working there.

Very few managers in large companies can throw around threats like that, and the ones who can realize it just makes them look unhinged like the Queen of Hearts in “Alice in Wonderland.” Incidentally, a couple of years ago, I was a contractor for Amazon for a very short time. One thing that stood out was that customers would email Bezos directly, or problems would bubble up to him in some other way, and he would respo…

That is pretty normal, both in the CEO or founder just asking or having to ask a question and the quickness and lengths that people go to to address it.

People don’t actually get credit for addressing the issue. People just get dinged for not addressing the issue quickly.

It is actually a red flag if a CEO or founder doesn’t behave this way since it means that they aren’t showing care and attention or that they are operating at the wrong level.

Post reply on HN