Software Architecture in Golang: Orchestrator Pattern

What is the Orchestrator Pattern? Adam Bellemare defines it in his book "Building Event Driven Microservices" as a "pattern where a central Microservice, issues commands to and awaits responses from subordinate worker Microservices".

■ Pros of using the Orchestrator Pattern:
■■ It's relatively easy to implement and maintain because all coordination is in one place.
■■ Workflow is easier to define because of the nature of the centralized orchestration.

■ Cons of using the Orchestrator Pattern:
■■ There's coupling between the orchestrator and services, any upstream changes require changes in the orchestrator.
■■ Single point of failure, because the orchestrator is in charge of the workflow, if it fails everything fails even the if the other services are working correctly.

== Relevant links

== All Go/Golang Playlists

== Socials

00:00 - Introduction to the Orchestrator Pattern for Microservices
01:19 - Example of implementing the Orchestrator Pattern in Golang
12:58 - Conclusion of the Orchestrator Pattern using Golang

=== Who am I?

Hello👋🏼! I'm Mario, a Hands-on Software Architect and Lead Backend Engineer with decades of professional experience building all kinds of software including on-premise Industrial Automation Systems, Linux Accessibility Desktop and Browser Components as well as Distributed Advertising Microservices.

The content I share includes different topics I've learned while working for small startups and large companies including the processes I've followed over the years for successfully delivering complex enterprise systems from start to end.

Subscribe if you like Software Development, Software Architecture and Systems Design!

Keep it up. Don't give up!

#golang #tutorial #microservices

=== Our Vlog Channel

=== Our affiliate links below

DISCLAIMER: Some of the links shared in the description are affiliate links. As a member of these affiliate programs, I earn a small commission from your purchases at no additional cost to you. I appreciate your support! 💖

[Alexyslozada]

Hi Mario, thanks for the video. It seems the total is returning 9 and that is wrong. Or I missed something?

[GabrielPozo]

Simple but effective example! Thanks for sharing!

[zema]

I really appreciate the effort that goes into these videos, many thanks!

[LucidGR]

Great videos, this channel deserves more subscribers.

[xabcyabc]

Ohh errGroup!!! I didn't know that this exist in golang😮, btw thanks marrio sir this video was so informative for me❤️

[farzadmf]

Thank you, nice video! And thank you for fixing your vim/neovim's signcolumn to prevent the text (code) from jumping around as you were typing

[pietart]

Thanks for the video, I saw a direct example of synchronous calls. Since most api calls are asynchronous, is the orchestrator the synchronizing only other service calls?

[jackn]

Great video! Really curious what LSP plugins you are using in your vim config. I use CoC right now but it doesn't look as fancy with your type definitions and icons. Do you have a vimrc or init.vim you could share?

[Marlem]

hi Mario! Could you please share your vim setup? it looks so cool!

[Kindafkglad]

Hi Mario thanks for sharing you knowledge, we really appreciate the effort, keep it up man.
I was wondering if you can list opensource projects (small or medium projects) that can be used as example regarding the golang software architecture and best practices? thanks in advance

[ophirraj]

Hi. Totally off topic. VIM colorscheme looks lit. Can I know the name?

[abcoflife]

Hi, great lesson, thank you so much, one question about the vi Editor, the Go syntax checker is very great I like it, can you please share the link for it please :))

[simajacob]

Love your content. Can you please make a full course? just a single course on Udemy or even a personal website. Full courses on go and microservices. and others go topic. We need one full course for each great topic. here it seems like there are many of information but not properly ordered. Please we need a full course for each great topic.