System architecture

Use these articles for Zbix CRM 1.2.0. Review each procedure’s prerequisites and qualification before acting.

• Application architecture overview — Use this reference to identify the component responsible for a request or delayed operation and to plan an operational handover without assuming additional infrastructure.
• Technology stack and dependency boundaries — Use the stack inventory for integration planning, support ownership and dependency review. It does not prescribe installing current upstream library versions into a released appliance.
• Frontend architecture and navigation — Use this article to understand page loading, navigation and client-side behavior when supporting a user or extending a compatible integration.
• Backend architecture and application services — Use the service boundaries to locate the correct support evidence and to avoid treating every visible page as an independent deployment service.
• Database architecture and transaction integrity — Use this reference to understand data ownership, migration boundaries and why supported application operations are necessary for consistent changes.
• CRM and commercial data relationships — Use the relationship model to prepare clean data, resolve lookup errors and understand the path from qualification to invoicing.
• Private files and generated document storage — Use this article when planning storage, investigating missing files or defining the scope of a recovery point.
• Background processing and durable jobs — Use this article to follow scheduled operations and to distinguish a queue delay from a completed or failed business operation.
• API validation and safe concurrency — Use this reference to resolve rejected forms and design clients that preserve user intent when data changes concurrently.