3 ms·
Reinventing all parts for every microservice sounds wasteful to me. Especially if they handle the same data and/or use the similar business logic.
by dx034 7y ago
Reinventing all parts for every microservice sounds wasteful to me. Especially if they handle the same data and/or use the similar business logic.
- kminehart 7y agoA common practice is to introduce services that handle shared functionality. One common example is, instead of having a shared library that reads & verifies JWTs, use a gateway service that handles this before requests reach the upstream service. This means changes to your organization's JWT code will only require a redeployment of one service, the JWT Auth service.
- dx034 7y agoBut that also for input handling, formatting or simple business libraries? Sure you could implement that as services but that would probably result in up to a hundred service calls for one customer interaction. Maybe it looks clean from an architecture perspective but I can't imagine how that'll result in a good user experience.
- kkapelon 7y agoLet me clarify because I wasn't clear in the parent comment. Microservices using shared libraries -> ok Microservices "suffering" from shared libraries -> not ok.