4 ms·
If we go with your definition then my app is a monolith with S3 and SQS which doesn't help me pinpoint where the potentially bad architecture thing is.
by Spivak 5y ago
If we go with your definition then my app is a monolith with S3 and SQS which doesn't help me pinpoint where the potentially bad architecture thing is.
- scottious 5y agoyeah -- your app is coupled to those services. I've definitely written code before that depended on a third party API only to have that API break on me. Granted, this is not something to worry about with S3 or SQS. > If we go with your definition then my app is a monolith with S3 and SQS okay sure, I agree that calling your app a monolith with S3 and SQS is ridiculous. The point is that we all may think that we're writing another S3 or SQS when we write our own micro-services. However, in practice maintaining a stable, backwards compatible, public API like that is quite costly and we usually end up re-implementing function calls as HTTP requests and then calling it "loosely coupled".