2 ms·
Authentication/sso, logging, metrics, persisted data stores (ie. sql server), caches (ie. redis), events, workflows and few others are all well known, understoo
by mirekrusin 4y ago
Authentication/sso, logging, metrics, persisted data stores (ie. sql server), caches (ie. redis), events, workflows and few others are all well known, understood, isolated behaviors with good implementations that doesn't need to be embedded/reinvented - it can and in many cases should run separately to your core service/s. It doesn't imply microservices in any way.
- rozularen 4y agoI'd argue the exact opposite and would say it's the perfect example of mixroservices architecture. you'd have one instance for your auth token generator, one for the gateway, one for the dashboard, and so on