Loading…
Topic
1 post about Apache Camel. Every summary links to the original.
See the idea
Apache Camel is shown as the integration path that brings application actions into one request workflow. The diagram clarifies real-time versus scheduled ingestion, mapping, merging, authorization, and audit.
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Uber built uAct to consolidate action items and approval requests generated by its many internal applications, addressing notifications that could be lost among email and follow-ups. It combines real-time fetching with scheduled offline ingestion through Apache Camel, stores requests, and merges them in received and sent views. Users can act through deep links or within uAct, where the Action Dispatcher authenticates and authorizes actions and the Audit Trail Provider records them for compliance. Its onion-architecture backend uses orchestrators, application-specific mappers, MySQL for requests and CacheFront for preferences, while parallelized paginated calls and strict timeouts support performance as integrations grow. The platform has been implemented across Uber and also provides configurable views, hiding, manager filters, observability, privacy controls, and planned Slack notifications, reporting, nudging, and additional integrations.
The best engineering reads, once a week.
