Please enable JavaScript.
Coggle requires JavaScript to display documents.
IPC - Coggle Diagram
IPC
Sync
REST
use HTTP
Benefit
Simple and familiar
Easy to test an HTTP API from browser, Postman, curl
HTTP is firewall friendly
Does not require any intermediate broker
Drawback
Only support request/response style of communication
Reduced availability. Both client and service must be available for the duration of the exchange.
Client must know the location of service instances
Service Discovery
Application Level
Client-side discovery pattern
Self registration pattern
Platform Level
3rd party registration pattern
Server-side discovery pattern
Fetching multiple resource in single request
Partial failure handling
From client side
Network Timeout
Rate limit from a client to a service
Circuit Breaker pattern
From unavailable service
Return default value
Return value from cache
gRPC
Interaction Styles
One to one
Request/Response
Async Req/Response
One way Noti
One to many
Publish/Subscribe
Publish/Async Response
Async
Broker-based messaging
Benefit
Loose coupling
Message buffering
Flexible communication
one way noti
pub sub
publish / async response
Cons
performance bottleneck
Single point of failure
Additional operational complexity
Challenge
Message ordering
Shard/Partition
Duplicate message
Idempotent message handler
Track message and discard duplicate
Transactional message
Transactional Outbox pattern
Polling publisher
Transaction log tailing pattern
CDC: Debezium...
DynamoDB stream