Consumers Clients
Web and mobile apps, partner systems, internal callers.
request over HTTPS
Integration
Enterprise integration
Quince Software delivers enterprise integration, cloud-native, on-premises or hybrid, with twelve-plus years behind it. Architecture, build, security design, security compliance, and the running of estates other people depend on.
Authorization is the firm's other discipline and has its own page. The two were delivered as separate engagements.
The shape of the work
One front door, many systems of record
Wider than the screen. Scroll the diagram sideways to follow it.
Reference architecture · integration
One runtime sits behind the gateway and managed file transfer
Backend services
Kubernetes or OpenShift on AWS, IBM Cloud or Azure · App Connect Enterprise in containers · MQ and Kafka as a managed service or in-cluster
API gateway Edge
One front door: routing, authentication and quotas.
routed to a service
Managed file transfer Files
Partner file drops and scheduled transfers.
batch received
Microservices ACE
One container per capability, all behind the gateway.
/orders · /invoices · /payments · /customers · /assortments · /pricing · /shipments
IBM MQ Queues
Transactional messages, delivered once and in order.
message queued
Apache Kafka Events
Event streams, replayable, for downstream consumers.
event published
Datastore State
Correlation keys, in-flight status and cached reference data.
CouchDB, or the client's own
SAP S/4HANA ERP
Finance, sales and distribution.
IDoc, JCo, BAPI
Salesforce CRM
Accounts, opportunities and cases.
REST API
E-commerce Shop
Orders, catalogue and stock from the storefront.
webhooks and REST
Payment and settlement Finance
Settlement files into the finance ledger.
files and messages
What we deliver
Architecture through to operations
Integration architecture and delivery
Architecture through to running code on the IBM stack: App Connect Enterprise and Integration Bus, MQ, API Connect and Cloud Pak for Integration, with Apache Kafka where the traffic is event-shaped.
Cloud, serverless and containers
Integration built on cloud platforms rather than on an appliance: AWS, IBM Cloud or Azure, with serverless functions, API gateways and event-driven flows, and containerised App Connect Enterprise runtimes on Kubernetes or OpenShift.
SAP integration
IDoc, JCo and BAPI interfaces, SD and retail flows, finance settlement interfaces, and e-commerce and payment integrations into SAP finance.
Security design
How an estate holds its credentials, secures traffic in transit, separates its environments, and what evidence the design leaves behind.
Running it, or leading the team that does
Managed integration services under an agreed SLA, managed file transfer modernisation, and integration team leadership, currently a six-engineer team at a global consumer-goods group.
Technologies
What the work runs on
- AWS
- IBM Cloud
- Azure
- SAP S/4HANA
- IBM App Connect Enterprise
- IBM Integration Bus
- IBM MQ
- Apache Kafka
- IBM API Connect
- Cloud Pak for Integration
- Salesforce
- CouchDB
- SAP IDoc
- SAP JCo
- SAP BAPI
- Serverless functions
- API gateways
- Kubernetes
- OpenShift
Industries served
- Consumer goods
- Retail
- Banking
- Automotive
- Pharma
- Telecom
- Petroleum
Compliance
Start with the estate you have
An integration engagement starts with what is already running, what it costs to keep running, and what has to change first.