Lesson 45 - Microservices Gateway Pattern

[kevinkkirimii]

For a small system, the cost of having multiple microservice gateways outweighs the benefits as opposed to a large system. Thank you though, your knowledge is invaluable.

[mqtt]

I can easily understand the benefit of the gateway pattern I had found in PAEE book of Martin Fowler applied here in the micro services domain. It is not clear to me the benefit of having multiple micro service gateways instead of one, but I may just need to study more on micro services. Keep up the good work

[yar]

Maybe i misunderstood it, but what the difference between this and adapter pattern which is supposed to transform data between protocols or domain data schemas.
Or its another kind of classification?

Thanx for your videos!

[omarbouaouina]

I would like to ask, if I may: can we have different patterns in a microservices architecture? To clarify my question: I understand the benefits of having an API Gateway, especially when dealing with cross cutting concerns. But, I want to ensure an asychronous type of communication between microservices, as well as some form of distributed transactions through orchestration/choreography.
I keep reading and watching videos about these topics to find a solution to check every box, but I have yet to find one.

[willrowan]

@~5:15 --> discussion of Apache Camel and Routes. In this model would there be one Apache Camel instance w/ multiple routes or multiple Camel instances each with one route.

[davideb]

So 20 Gateway microservices mean 20 separate projects, repositories, CI/CD pipelines, and hosts. Right?