Skip to main content
PreparationZone Logo
PrepZone

Processes, Services, and systemd

PID management, signals, systemd units, and why containers changed how we think about services.

Pass checkpoint below

Why this matters

  • This topic directly affects how reliably BookStore reaches production — processes are running programs; systemd (or container pid 1) defines how bookstore services start, restart, and log..
  • Interviewers connect hands-on commands and manifests to real delivery stories, not buzzwords.
  • Later modules assume you can explain both the why and the concrete file or command involved.
  • Platform maturity shows up when teams automate this instead of relying on tribal knowledge.
Virtual Machine
App AGuest OS
HypervisorFull OS per VM
Host OS + Hardware
Container
App AContainer
App BContainer
Container runtimeShared kernel
Host OS + Hardware
VMs virtualise hardware; containers share the host kernel and isolate with namespaces and cgroups.

Processes and signals

PID 1 in VMs vs containers: BookStore engineers treat this as part of the standard path from laptop to processes services systemd readiness. Document decisions in the team runbook so on-call knows which knobs exist.

Key ideas

  • Processes and signals — primary idea for processes-services-systemd
  • BookStore context — catalog API, checkout, and inventory services share the same pattern
  • Automation — prefer pipeline jobs over manual SSH steps
  • Verification — staging must prove the change before prod traffic

systemd units for legacy hosts

When BookStore still runs on VMs: When staging matches production architecture, BookStore catches misconfigurations early. Pair this section's practice with observability dashboards to confirm behavior under load.

Key ideas

  • systemd units for legacy hosts — operational detail
  • Rollback — know how to revert without rebuilding artefacts
  • Security — least privilege for deploy roles
  • Documentation — link runbooks from the service README

Production checklist

Before promoting BookStore changes tied to this topic, run automated tests, inspect artefact immutability (image digest or JAR checksum), execute a staging smoke test on /actuator/health, and watch error-rate dashboards for thirty minutes after prod rollout.

Key ideas

  • Staging soak — validate under synthetic load
  • Change ticket — attach pipeline URL and artefact digest
  • On-call — page owner stays on dashboards during rollout
  • Post-deploy — record metrics baseline for comparison
Java
[Unit]
Description=BookStore API (legacy VM)
After=network.target

[Service]
ExecStart=/opt/bookstore/bin/api.sh
Restart=on-failure
User=bookstore

[Install]
WantedBy=multi-user.target

Quick recall

Everything you need if you only revisit this box.

  • BookStore uses processes services systemd as a standard delivery practice.
  • Prefer automation and versioned config over manual server changes.
  • Staging proves changes before customer-facing promotion.
  • Observability confirms success — do not rely on silence alone.
  • Rollback plans must be tested, not invented during an outage.
  • Security and least privilege apply to every pipeline and cluster role.

Test yourself

Answer these before moving on — recall is what makes it stick.

Checkpoint quiz

Pass 2 of 3 to verify this article on your path — scrolling alone does not count.

Question 1 of 3

A public method in a service calls another @Transactional method in the same class. What happens?