Component diagram

Next you can zoom in and decompose a container to describe the components that reside inside it; including their responsibilities and the technology/implementation details.

Example

Diagram key

Scope

A single container.

Primary elements

Components within the container in scope.

Supporting elements

Containers (within the software system in scope) plus people and software systems directly connected to the components.

Intended audience

Software architects and developers.

Recommended?

No, only create component diagrams if you feel they add value, and consider automating their creation for long-lived documentation.