Scribd
Upload
57 views

Micro Services

This document discusses eight common fallacies of distributed computing systems and the network being reliable, latency being zero, infinite bandwidth, a secure network, static topology, single administrator, zero transport costs, and homogeneity. It also advocates for a "smart endpoints and dumb pipes" design where asynchronous communication is favored over complex integration platforms to reduce organizational complexity. Finally, it outlines different types of synchronous and asynchronous communication for single and multiple receivers like HTTP, AMQP, and publish-subscribe patterns.

Uploaded by

mansha99
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
57 views

Micro Services

This document discusses eight common fallacies of distributed computing systems and the network being reliable, latency being zero, infinite bandwidth, a secure network, static topology, single administrator, zero transport costs, and homogeneity. It also advocates for a "smart endpoints and dumb pipes" design where asynchronous communication is favored over complex integration platforms to reduce organizational complexity. Finally, it outlines different types of synchronous and asynchronous communication for single and multiple receivers like HTTP, AMQP, and publish-subscribe patterns.

Uploaded by

mansha99
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

MicroServices 1/3

_________________________________________________________________________________

Eight fallacies of distributed computing


The network is reliable
Latency is zero
Bandwidth is infinite
The network is secure
Topology doesn't change
There is one administrator
Transport cost is zero
The network is homogeneous

Smart endpoints and dumb pipes


A design principle that favors basic, time-tested,
asynchronous communication mechanisms over complex integration
platforms. Teams that are expected to rapidly deploy features
and improvements are typically looking for ways to cut down on
organizational complexity. Your bus may be used for
communication but not to govern this communication.

Communication Types
Synchronous Asynchronous

Single HTTP/Command Pattern AMQP/Command Pattern


receiver

Multiple HTTP/Publish Subscribe AMQP/Publish Subscribe


Receiver

_________________________________________________________________________
Manish Sharma [email protected]
MicroServices 2/3
_________________________________________________________________________________

_________________________________________________________________________
Manish Sharma [email protected]
MicroServices 3/3
_________________________________________________________________________________

Asynchronous event-driven communication

_________________________________________________________________________
Manish Sharma [email protected]

You might also like