4 ms·
Circuit breaker is a design pattern, not an architecture pattern. Event sourcing is badly written. I'm guessing that one is supposed to look at a seperate even
by Spearchucker 6y ago
Circuit breaker is a design pattern, not an architecture pattern.
Event sourcing is badly written. I'm guessing that one is supposed to look at a seperate event log instead of querying the data directly.
Not understanding the Sidecar pattern either. Does L4/L7 imply L4, 5 6 and 7, or just L4 (transport layer) and L7 (application layer)? Does sidecar then simply suggest seperating application logic from cross-cutting concerns (communication, security, logging etc.)?
- anon73044 6y agoI've only ever seen the sidecar pattern described with containers. https://docs.microsoft.com/en-us/azure/architecture/patterns/sidecar https://docs.microsoft.com/en-us/azure/architecture/patterns...
- deleted 6y ago[deleted]
- legerdemain 6y agoYes, basically as you guessed. Applications receive input, manage local resources, and produce output. The sidecar proxy is their interface with the world. The proxy handles cross-cutting infrastructure concerns: service discovery, federation, distributed tracing, and so on. Blog posts about Envoy proxy as a sidecar in a service mesh context should offer plenty of examples.