Contents

# Why HTTP is a bad choice for interservice communication

[WIP]

Downsides of HTTP:
* inherently synchronous
  * timeouts
  * retries
* one-to-one, no pub/sub
* additional work required:
  * network
  * service discovery
  * routing
  * load balancing
  * authentication/authorization


Pro's of HTTP:
* synchronous communication is simple
* HTTP as technology is well known by engineers

Version data entries

9 entries across 9 versions & 1 rubygems

Version	Path
mimi-messaging-1.2.7	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.2.6	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.2.5	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.2.4	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.2.2	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.2.1	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.1.1	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.1.0	docs/Why_HTTP_is_a_bad_choice.md
mimi-messaging-1.0.0	docs/Why_HTTP_is_a_bad_choice.md