How to implement Design Pattern for a microservice proxy?

Asked

Viewed 78 times

0

Soon we will make our applications through Middleware, I know that the authentication of the systems will be through Oauth2, but I have the following doubt:

Where I should start studying related subjects and how I could adapt the applications we already have to a Pattern design that works at this level of architecture. Could someone give me a simple example of how to implement an email system for example?

  • 1

    I think you’re using the term "Design Pattern" inappropriately. They will only indicate a way to solve a particular problem, not the application architecture as a whole. What you want is not solved by applying a single Pattern design for example, you need to define the boundaries of your application and how the dots will connect. As I have no practice with the technologies mentioned, I can’t help you.

  • As far as I know, is microservice a Pattern or not? What I need to know is how to do it...

  • Yes. It’s a pattern, but maybe not a drawing. When you say "Design Pattern" this refers more to a solution of a "small" problem and not an architectural pattern. Microservices have been gaining popularity lately, but I would advise you to do a lot of research on the concept before going into an implementation.I say this because I don’t know any "Hello World with microservices", although I don’t doubt it exists. I will point you to a podcast that I believe you can add in your search: http://technologyRetogether.com.br/2015/08/03/microsservicos-com-renan-martins/

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.