Skip to main content

System Context

Summary​

HR Suit serves HR, employee, customer-administration, and platform-administration users through two web portals backed by a transitional monolith-and-services architecture.

Audience​

  • Enterprise customers and implementation partners
  • Developers, QA engineers, and DevOps engineers
  • Solution architects and product owners

Overview​

The client HRMS portal serves tenant-scoped workforce use cases. The super-admin portal serves platform-level administration. Requests enter through a gateway, which routes them to the active monolith or an extracted service according to current cutover configuration.

The following diagram is conceptual. It shows verified component classes and dependency types without disclosing environment-specific identifiers.

The PostgreSQL node represents a platform database technology and multiple logical ownership boundaries, not one universally shared service schema. Document storage and email are provider dependencies whose deployment choices can vary.

System boundaries​

  • Inside HR Suit: web portals, gateway, active monolith, extracted services, application data ownership, and integration processing.
  • Platform dependencies: PostgreSQL and RabbitMQ.
  • Provider dependencies: document storage and email delivery.
  • Hosting: repository deployment assets support an AWS container-service model at a high level; actual deployed topology requires environment confirmation.

See Also​

Keywords​

  • System context
  • Application boundary
  • External dependencies

Revision Information​

  • Last reviewed: 2026-07-14
  • Owner: architecture-team
  • Status: Draft