Solutions
Technical notes on integration, cloud and data.
Design criteria and technical analysis on Oracle Cloud integrations, databases and software architecture, with official sources.
- Error handling and reprocessing in Oracle Integration 3: a model that neither loses nor duplicates work A misclassified fault becomes either a duplicated operation or lost work. A model for fault classification, visibility and recovery for integrations in Oracle Integration 3.
- Queue architecture: acknowledgement, idempotency, retries and dead letters A queue decouples systems, but it does not remove pending work: it moves it. Design principles for acknowledging at the right moment, avoiding duplicate effects, retrying with judgment and operating the dead-letter queue.
- Integration patterns in Oracle Integration 3: choosing the trigger What starts an integration determines how a delay is detected, how a duplicate is prevented and how a failure is recovered. Criteria for choosing between Application, Event and Schedule in Oracle Integration 3.
- Baseline network in OCI: VCN, subnets, gateways and traffic control A tenancy's first network tends to become the foundation for everything that follows. Criteria for designing it from approved flows, and a procedure for validating it before applications go live.
///// CONTACT
Facing something similar?
Tell us what you are working on and we will look at it together.
Based in Guatemala City (UTC−6), working with organizations in Central America and the United States during U.S. business hours, in English and Spanish.