![]() ![]() 90% of the wait is coming from the email service. ![]() Let's say the user waits very long for checkout and email to finish. they're not necessarily related but inevitably we implement them together when scaling one or the other.įor example given this microservice architecture -> In the real-world when you onboard to a new company you'll find yourself asking questions like Just remember that these are concepts to help you understand an existing system, or help you decide how you would build your system. Do you go for the larger slices, mixed, small ones or meatier ones? Just like how our systems can decide intelligently what events to trigger next. Which one to eat first and next is thinking event-driven. Let's take pizza for example, deciding whether to cut it in squares or triangular, or how big/small the slices are is thinking microservices. Another benefit of microservice is deployability, the smaller the service the faster to test and deploy. If FB was "monolith", one service going down could have taken down the whole site. One benefit of this is "separation of concerns", so for example if newsfeed goes down we can still continue to upload photos and chat our friends. For example, Facebook's newsfeed service is independent of other services like Profile, photos and messaging. Microservice is an approach to designing our system where we make our services decoupled to one another or at least we try our best to. Such techniques can be pub/sub, long polling, Queueing, websockets and etc. More likely than not we want asynchronous communication. Is microservice architecture a subset of event driven architecture or is there something more to it that I need to figure out.Įvent Driven Architecture is a system design concept where we use "techniques" to achieve synchronous or asynchronous communication in our system. I have been going through some system design videos and learnt about microservice architecture and event-driven architecture. Is microservice architecture with messaging queues a subset of event driven architecture or is there something more to it that I need to figure out. I have been going through some system design videos and learnt about microservice architecture using message queues and event-driven architecture.īut I don't seem to find any substantial point of difference between the two.īoth have different components/services publishing or subscribing to eventBus/messagingQueues and performing the tasks associated with the published event. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |