This shows the architecture of LinkedIn.

As is evident from this diagram, it is a process view. It

shows various components and how they interact with
each other at runtime.

However, this also contains elements of a logical view.

For example, the Web App box on the top-left shows
its constituent modules/subsystems: the GUI Layer, the
BL Layer and the session cache.
This also contains more information about the nature
of the various interactions. For instance, the interaction
between the Web App and the Cloud is through httprpc or jms calls. The Web App has a read-only

interaction with the ReplicaDB, whereas it has both

read/write permissions while interacting with the Core
Database.
This diagram does not show the physical view (for
example, the implementation of the database servers)
or the development view of the system (for example,
which parts of the system are developed and
maintained by LinkedIn, and which parts are
outsourced for development and maintenance, and to
whom).