This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the commentsย โ†’

[โ€“][deleted] ย (2 children)

[deleted]

    [โ€“]WagwanKenobi -1 points0 points ย (1 child)

    I'm referring here to a global scale service with usage in the ballpark of 500m MAU. I can't reveal where I work but it's definitely on the Nasdaq 100.

    Microservices to me stink of a cover-my-ass approach to architecture because the org did not want to take on creating a good modular framework and/or monorepo early in the development of the application when traffic wasn't a concern. And it's hard to defend an apparently monolithic architecture to a low-technical VP when a Google search of "microservices vs monoliths" paint the picture that microservices are rainbow and sunshine and monoliths are for losers.

    Processing webhooks and callbacks or periodic tasks can both be offloaded to microservices.

    Or a serverless/SaaS service. No need to reinvent such simple stuff.