Skip to main content

πŸ—οΈ Architecture Overview

What lives here: BeWith's product/system architecture β€” services, data flows, infrastructure, the structure of what we run in production.

Use vs. siblings: Methodology is how we work (including the AI Engineering Strategy β€” note: that doc is the AI-engineering architecture, not the product). Architecture is what we built. Specific decisions are recorded as ADRs.

Last updated: 2026-06-03 Β· Owner: Engineering Lead

BeWith is a cloud-native SaaS platform on AWS, serving two product lines: the Israeli line (coing.co) and the international line (withsites.com / withapps.io). It is built around two backends β€” a PHP/Yii2 monolith that is the system of record, and a NestJS "API v2" microservice monorepo β€” backed by MySQL, MongoDB, Redis, OpenSearch, and SQS, with web (React/Next, Angular) and mobile (Flutter) clients.

In this section​

  • System Architecture β€” the services, the repoβ†’owns map, the MySQL/Mongo/Redis/OpenSearch/SQS data-store boundaries, and the tenancy model. Start here for "who owns what / where does data live".
  • Infrastructure & Environments β€” the two compute platforms (EKS primary / ECS legacy), the four environments, how code deploys (the tag contract), and observability. Start here for "what runs where / how it ships / where to look when it breaks".
  • Environments Portal β€” the live launcher: clickable links to every app, API, and migration pipeline across all four environments. The "take me there" companion to the reference doc above.

Status​

This section is being built from verified reads of the live repos (replacing earlier placeholder content). The broader Confluence architecture survey migration is tracked in proposal-2026-05-31. Where a claim is not yet verified against the live system it is flagged unconfirmed in the doc that carries it.