Microservice Architecture Considerations for Code Recovery, Security, and Database Sharing

Question

I have the following questions about microservice architecture

• How are common code / utility libraries reused between different microservices? Where is this common code also being developed

• In my microservice, some services are intended for clients, and some may be internal (for using other microservices). What is the best option for securing internal services?

• What if two microservices must use the same database? Say they perform completely different operations, but use the same database table?

• Microservices mostly touch the back, but the GUI will be the same. In this case, a web site update is also required for each microservice deployment. Is this considered a disadvantage?

Answer 1

DISCLAIMER: These are answers based on my point of view, based on my experience working with various microservice-based architectures.

• ( ). , , , . , , , . , depdencies.

• , , . , , . - ( , http://jwt.io/, , ). .

• - - , 1. , , "" , . , , .

• , . . (, /v1/messages, REST HTTP), . , , - .

, ( ), , .