Camel Integration Layer — Knowledge Transfer¶
A short onboarding guide for developers joining the PopSockets integration team.
It's written for engineers coming from a Salesforce background (Apex, flows, platform events) who are picking up our Java + Apache Camel integration platform. You don't need to know Java or Camel yet — that's the point.
How to use this¶
This is a KT handout, not a reference manual. Each page is a screen or two. Read them in order the first time; come back to #7 as a cheat sheet later.
| # | Page | What you get |
|---|---|---|
| 0 | Orientation | What this codebase is and why it exists |
| 1 | From Salesforce to Camel | Your mental model, translated |
| 2 | Tech stack & anatomy of a service | The stack and how one service is laid out |
| 3 | How the services talk | Service Bus, APIM, Config Server, the exp/prc/sys layers |
| 4 | The business domain | Orders, EDI, and the "life of an order" |
| 5 | Run, build & test locally | Getting a service up on your machine |
| 6 | Deployment & branching | How code gets to each environment (and the rules) |
| 7 | Service inventory & glossary | Every cm-* service + an acronym decoder |
The 30-second version¶
This codebase is the middleware that moves orders, shipments, products, and inventory between the systems that run PopSockets — the storefront, the ERP, the warehouses, and our retail trading partners. It's ~20 small Spring Boot services built on Apache Camel. It replaced a legacy MuleSoft platform.
If you remember one thing: we rarely own the data — we move and translate it. Most of the job is receive → validate → transform → forward → acknowledge, and handling what happens when a step fails.
When you want the deeper reference
This handout gets you oriented. The rest of this site is the reference layer for the same systems, at production depth:
- Architecture — the full "Big Picture" topology + the core sequence flows.
- Camel Topology — every
cm-*service with deployment status (what's live, retiring, nonprod-only). - Endpoint & Environment Map — the real per-environment addresses for everything Camel talks to.
Where a KT page skims a topic, it links to the deeper page. Follow those when you're ready to go from "oriented" to "hands-on."