Backend Architecture

Learn the global structure of the backend of Diffgram


Here is a high level overview of the overall backend architecture installed in a k8s setting. The UI, which represents nearly half the codebase, is only represented as an entry/exit point in this Diagram.

This diagram leaves out a lot of technical detail and is meant as a high level overview.
Generally the default service is the primary interaction with external interfaces. There are some exceptions.

Diffgram integrates with "external" systems including blob stores, databases, model training providers etc.
A basic installation needs only one database, which is usually reserved exclusively for Diffgram. Similarly we require some blob storage for artifacts generated by Diffgram. Then there are interactions with external providers that may not be reserved specifically for Diffgram.