Live data from Hacker News

McDonalds Event Driven Architecture

medium.com

11–20 of 134 posts

Re: McDonalds Event Driven Architecture

#11
post #5

why does everything have to be microservice oriented and what's wrong with a simple monlithic application that runs the whole thing? also, when are those ice cream machines going to get fixed?

To your point, Shopify's monolith was handling 1.27M requests/sec on Black Friday: https://twitter.com/ShopifyEng/status/1597983918900510720 Thread: https://threadreaderapp.com/thread/1597983918900510720.html

But ruby is too slow!

Re: McDonalds Event Driven Architecture

#12
post #5

why does everything have to be microservice oriented and what's wrong with a simple monlithic application that runs the whole thing? also, when are those ice cream machines going to get fixed?

Well, I mean really most of the micro service architectures are just monoliths with network calls between the components.

yeah, so what about locking? it must be a nightmare to make sure that the components all work together as intended...

Re: McDonalds Event Driven Architecture

#13
post #5

why does everything have to be microservice oriented and what's wrong with a simple monlithic application that runs the whole thing? also, when are those ice cream machines going to get fixed?

This is a very informative YouTube video on that very subject (ice cream machines): https://www.youtube.com/watch?v=SrDEtSlqJC4

Re: McDonalds Event Driven Architecture

#14
post #2

While this satisfies some idle curiosity, I don't really get what justifies spending the resources in posting such stuff. Is this a recruitment tactic somehow for such companies?

Can I get promoted to Manager if I get a degree in Hamburger-data-ology?

From what I can tell the career path is into Corporate hell.

https://www.uopeople.edu/blog/hamburger-education-inside-mcd...

Re: McDonalds Event Driven Architecture

#16
post #5

why does everything have to be microservice oriented and what's wrong with a simple monlithic application that runs the whole thing? also, when are those ice cream machines going to get fixed?

Well, I mean really most of the micro service architectures are just monoliths with network calls between the components.

[deleted]

Re: McDonalds Event Driven Architecture

#17
post #11

Earlier quoted context omitted.

To your point, Shopify's monolith was handling 1.27M requests/sec on Black Friday: https://twitter.com/ShopifyEng/status/1597983918900510720 Thread: https://threadreaderapp.com/thread/1597983918900510720.html

But ruby is too slow!

Lots of their code is in Go

Re: McDonalds Event Driven Architecture

#18
post #5

why does everything have to be microservice oriented and what's wrong with a simple monlithic application that runs the whole thing? also, when are those ice cream machines going to get fixed?

Well, I mean really most of the micro service architectures are just monoliths with network calls between the components.

That's called distributed monolith. It's pretty much guaranteed to happen if the developers don't introduce a lot of redundancy while splitting up the services.

Re: McDonalds Event Driven Architecture

#19
post #12

Earlier quoted context omitted.

Well, I mean really most of the micro service architectures are just monoliths with network calls between the components.

yeah, so what about locking? it must be a nightmare to make sure that the components all work together as intended...

> yeah, so what about locking?

POST /lock

This is only a slight exaggeration over some of the stuff I've seen people try to pull.

Re: McDonalds Event Driven Architecture

#20
post #5

why does everything have to be microservice oriented and what's wrong with a simple monlithic application that runs the whole thing? also, when are those ice cream machines going to get fixed?

In your monolith if you offload a request to a queue and have a background process processing the queue messages, what do you call that module processing messages? Is it a component of your monolith? I think a lot of teams would call it a microservice, I could see some people considering it a component of a service.

Unless you're confounding microservices w/ async architectures and saying to drop asynchronous patterns like this all together.

Post reply on HN