APIs, integrations & distributed systems

An HTTP API style where resources are requested and updated over the web. It is used when systems need to exchange data that way.

An API style where a client asks for the fields it needs. It is used when that query style fits the product.

A remote-call protocol for services that exchange structured data. It is used between services when that protocol fits.

An XML protocol for exchanging messages between systems. It is used when an existing system already speaks it.

A protocol for messages in both directions over a long-lived connection. It is used when the product needs live updates.

A front door that routes API calls to the services behind it. It is used when several services share one entry point.

A log for events that other services consume. It is used when the product passes work through a stream of events.

A message broker for work passed between processes. It is used when the product needs that kind of queue.

A message broker for work passed between systems. It is used when an existing system already uses it.

A message broker used between enterprise systems. It is used when an existing system already uses it.

An in-memory store for cache, short-lived data, and queues. It is used when the product needs that kind of store.

A Python queue for work that runs outside the web request. It is used when a product needs that kind of background job.

Connections between a product and systems the company already uses. The other system depends on the project.

Work that runs after the web request has finished. It is used when a product needs that kind of job.