Application architecture overview
Overview
Section titled “Overview”Zbix CRM is a modular application with a browser interface, an HTTP API, a separate background worker, PostgreSQL and private file storage. The API and worker share the same domain models and durable state. The browser reaches application services through the web gateway. Optional SMTP and Microsoft Graph connections extend communications; the core CRM does not require a connected Microsoft tenant.
Purpose
Section titled “Purpose”Use this reference to identify the component responsible for a request or delayed operation and to plan an operational handover without assuming additional infrastructure.
Prerequisites
Section titled “Prerequisites”-
Access to the release manifest and an administrator account for System Health.
-
A deployment-specific topology showing the gateway and persistent stores.
Procedure
Section titled “Procedure”-
Open Administration > System Health and record the displayed migration and available runtime identity values in the private handover record.
-
Identify the browser-to-gateway route, then the gateway-to-API route. Ordinary CRM pages and API calls share the application origin.
-
Identify PostgreSQL and the private file store used by both API and worker. Record their protected backup scope through the approved recovery process.
-
Inspect worker heartbeat and queue summaries separately from database reachability. A working page proves neither scheduled execution nor external delivery.
-
For an integration issue, follow the provider selected for that operation. SMTP, Graph and local mock delivery have different outcomes and prerequisites.
Expected result
Section titled “Expected result”The support team can trace browser requests, transactions, queued work and stored documents to their responsible component.
Screenshots and diagrams
Section titled “Screenshots and diagrams”
Important notes
Section titled “Important notes”-
No Redis, RabbitMQ or external search engine is required by this implementation. PostgreSQL stores job state and execution coordination.
-
The gateway differs by deployment package. Use the Linux or Windows topology for concrete service and port details.
-
A source tag identifies code. A screenshot or health response is separate evidence of the running installation. Unreported runtime identity must not be treated as a confirmed match.
Troubleshooting
Section titled “Troubleshooting”-
Pages load but jobs do not complete: inspect the worker and relevant queue, then the current actor permissions.
-
Files are unavailable despite visible records: verify private storage and attachment scan evidence rather than assuming a database failure.
Related articles
Section titled “Related articles”Search the guides or talk to the ZBIX team.
Software products, application engineering and IT services from Zbix Technologies.
Visit our company website ↗