Vacancy API And Persistence Surface

Route / API Surface

| Surface | Current path | Classification | Notes | | --- | --- | --- | --- | | Public vacancy list | GET /vacancies | MIXED / compatibility route surface | Uses preferred vacancy read repository, but that repository still unions projection-backed rows with legacy vacancies. | | Public vacancy detail | GET /vacancies/:id | MIXED / compatibility route surface | Checks projection detail first, then falls back to legacy vacancies. | | Applicant application list | GET /vacancy-applications/me | stable route surface | Requires auth; reads from my_vacancy_applications_view. | | Submit vacancy application | POST /vacancy-applications | stable route surface | Requires auth and vacancy-application submit capability. | | Withdraw vacancy application | POST /vacancy-applications/:id/withdraw | stable route surface | Requires auth and vacancy-application withdraw capability. | | Review actions | POST /vacancy-applications/:id/shortlist, /reject, /accept | stable route surface | Auth-protected owner-side application decisions. | | Posting create/update | POST /vacancy-postings, PATCH /vacancy-postings/:id | stable route surface | Core vacancy posting mutations. | | Posting publish/close/reopen | POST /vacancy-postings/:id/publish, /close, /reopen | stable route surface | Clear lifecycle mutation surface. | | Owner posting list/detail | GET /owner/vacancy-postings, GET /owner/vacancy-postings/:id | stable route surface | Uses vacancy-owned reads over vacancy_postings. | | Owner applications list/detail | GET /owner/vacancy-applications, GET /owner/vacancy-applications/:id | stable route surface | Reads from direct joins over vacancy_applications + vacancy_postings. | | Posting applications by posting | GET /vacancy-postings/:id/applications | mostly stable, lightly composed | Owner check and application list are vacancy-owned; the response also loads vacancy summary through the broader public finder. |

API Gateway Surface

| Gateway route module | Target resolution | Classification | Notes | | --- | --- | --- | --- | | services/api/src/routes/vacancies.ts | VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL | stable shared seam | Ready for extracted runtime targeting. | | services/api/src/routes/vacancy-postings.ts | VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL | stable shared seam | Includes auth-protected posting mutations and review list-by-posting. | | services/api/src/routes/vacancy-applications.ts | VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL | stable shared seam | Includes submit, me-list, owner decision, withdraw. | | services/api/src/routes/owner-vacancy-postings.ts | VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL | stable shared seam | Owner/internal read path already isolated at gateway level. | | services/api/src/routes/owner-vacancy-applications.ts | VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL | stable shared seam | Same. |

Persistence Surface

Clearly vacancy-owned persistence

Created in vacancy write-model migration lineage:

• vacancy_postings
• vacancy_applications
• vacancy_postings_view
• vacancy_posting_detail_view
• my_vacancy_applications_view
• vacancy_applications_by_posting_view

These are the real current vacancy write/read-model surfaces.

Compatibility residue

Legacy public discovery table:

• vacancies

This table is still part of public vacancy truth because VacancyReadRepository.listAllVacancies() and findVacancyById() fall back to it when no projection-backed posting exists.

Migration Readiness Notes

Vacancy-dominant migration surfaces:

• 0032_vacancy_write_model.sql
• 0044_add_details_json_to_views.sql

Mixed vacancy/accommodation context surfaces:

• 0042_vacancy_accommodation_context.sql
• 0043_vacancy_accommodation_declaration_details.sql

Legacy compatibility residue:

• 0005_vacancies_accommodations.sql

Read Surface Readiness

Already relatively clean

• owner vacancy posting reads
• owner vacancy application reads
• applicant vacancy application reads
• posting/application mutation paths

Still mixed

• public vacancy list
• public vacancy detail

Why they are mixed

The public routes are not shell-mixed because of auth or gateway composition. They are mixed because the preferred vacancy repository still treats the legacy vacancies catalog as fallback truth.

Extraction Notes

Best current extraction shape:

• move posting and application backend core first
• keep gateway seam unchanged
• either:
  • carry public vacancy compatibility residue explicitly for an early extraction, or
  • clean public discovery before cutover if the extracted service is expected to own canonical public truth immediately

This makes Vacancy less like ICPI or post-cutover Accommodation, where runtime truth was cleaner before final cutover.