search

stratospheric-dev / stratospheric

All you need to know to get your Spring Boot application into production with AWS 🍃
https://stratospheric.dev
Apache License 2.0
266 stars 188 forks source link

Need more explanation about microservices #112

Closed surkoff-v closed 2 years ago

surkoff-v commented 2 years ago

What can we improve?

Hello, first of all thanks for the great book ,i've just finished. Help me understand how implement some microservices patterns in aws with Spring Boot. When I run microservices on my server I use Spring Cloud. And for service discovery for example I use @EnableEurekaServer for server @EnableDiscoveryClient for client. What I have to use for service discovery and clients in aws? In book I haven't found such explanation. Could you help me may be with some link with explanation. Am I right that in aws I don't need to use Spring Cloud at all? But what I should use instead. PS: I sent the same on email

Version

Latest

Suggested Changes

No response

BjoernKW commented 2 years ago

Hi, thanks for getting in touch. Unfortunately, these specific patterns and microservices in general are beyond the scope of "Stratospheric - From Zero to Production with Spring Boot and AWS".

These links might help you get started with this subject, though:

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/service-discovery.html https://tomgregory.com/how-to-deploy-eureka-into-aws-ecs/

surkoff-v commented 2 years ago

Thanks a lot for the links. I think this topic in next edition of the book would be great. Because nowadays most of the people using clouds for microservices development.

On Mon, Jun 13, 2022, 23:38 Björn Wilmsmann @.***> wrote:

Hi, thanks for getting in touch. Unfortunately, these specific patterns and microservices in general are beyond the scope of "Stratospheric - From Zero to Production with Spring Boot and AWS".

These links might help you to get started with this subject, though:

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html

https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/service-discovery.html https://tomgregory.com/how-to-deploy-eureka-into-aws-ecs/

— Reply to this email directly, view it on GitHub https://github.com/stratospheric-dev/stratospheric/issues/112#issuecomment-1154414060, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGMSI5T7GYDB5L6C7HL236DVO6L4FANCNFSM5YVB3OSQ . You are receiving this because you authored the thread.Message ID: @.***>

rieckpil commented 2 years ago

There's no need for most of the Spring Cloud projects (except Spring Cloud AWS). For example, service discovery comes out of the box with the ALB (Load Balancer). You can access your microservices with a stable domain name and the load balancer internally "discovers" all your instances.

Also, the Spring Cloud Config server is not needed, as with the AWS Parameter Store or the Secret Manager you can outsource the configuration values.

We recommend using as many cloud services as possible (where it makes sense) to avoid any maintenance efforts for a self-hosted Eureka or Spring Cloud Config Server.

surkoff-v commented 2 years ago

Thanks for the advise. I have found in articles that you colleague sent me that there exists approach for service discovery with Cloud Map. What approach should be used and when, Service discovery ELB (ALB) based or Cloud Map based? Some articles say that Cloud Map based is client side approach and therefor is faster. What is your opinion?

rieckpil commented 2 years ago

I've never worked with Cloud Map so far and hence can only vote for ELB :D