Comment by anth_anm
7 years ago
They don't, they write a library and others consume it.
It's not a "you must find some data or service to expose". If you have data and someone wants to use it, they do it via service.
7 years ago
They don't, they write a library and others consume it.
It's not a "you must find some data or service to expose". If you have data and someone wants to use it, they do it via service.
ala tell, don't ask.
https://martinfowler.com/bliki/TellDontAsk.html
I'd also like to point out that with all design decisions there are trade offs. Bezos made these trade offs specifically with Amazon's scale in mind and likely would not make the same trade offs with a team of 5 devs or even a team of a thousand devs that had good habbits around adhering to data boundries.
Clearly the dev culture at Amazon had a habbit of abusing those boundries or it wouldn't have gotten to the point where such a black and white mandate made a net positive change to the status quo.
> Bezos made these trade offs specifically with Amazon's scale
It's more nuanced for Amazon - they intentionally ignored language skills when looking to hire good developers (difficult in 90's Seattle), so the end result was a hodgepodge of services written in many different languages talking any number of protocols which including Service A directly accessing the database of Service M. This mandate was his answer to teams complaining about working with each other and the bullshit they had to go through when integrating features across service boundaries to get things done.
The Sql services started without any data. The service started with empty tables. But yet they have an Sql service.
Nobody said you couldn't share, communicate or transfer ownership of your data to another service.
I'd say you're being a pedant but you're not even technically correct.
Are you getting off on being deliberately obstinate?