---
title: "Discussion on \"Designing a Reliable Integration Service in Spring Boot: From Webhook to Internal APIs\" | Hashnode"
description: "Discussion on \"Designing a Reliable Integration Service in Spring Boot: From Webhook to Internal APIs\". A common enterprise problem: data is collected in one system (an online form, a partner portal, a CRM), and a person copies it into several internal systems by hand. It's slow and full of typos. So yo"
url: "https://hashnode.com/posts/designing-a-reliable-integration-service-in-spring-boot-from-webhook-to-internal-apis/6ad91073f8e83c852bb7815d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Designing a Reliable Integration Service in Spring Boot: From Webhook to Internal APIs](https://manishchavan.hashnode.dev/designing-a-reliable-integration-service-in-spring-boot-from-webhook-to-internal-apis?utm_source=hashnode&utm_medium=feed)

A common enterprise problem: data is collected in one system (an online form, a partner portal, a CRM), and a person copies it into several internal systems by hand. It's slow and full of typos. So yo

Oct 21 · 5 min read · manishchavan.hashnode.dev  
Read the article

-   [#spring-boot](https://hashnode.com/tag/spring-boot)
-   [#java](https://hashnode.com/tag/java)
-   [#webhooks](https://hashnode.com/tag/webhooks)
-   [#system-design](https://hashnode.com/tag/system-design)

## Written by

[Manish Chavan](https://hashnode.com/@manishchavan)

@manishchavan · Canada

  
[View profile](https://hashnode.com/@manishchavan)

Hi I'm Manish| Back-end developer | Full stack developer | Passionate about coding

Experienced Full stack Developer with over 6 years of expertise in creating intuitive user interfaces. Specializing in JavaScript, I have a comprehensive understanding of the entire software lifecycle and can effortlessly transition between backend and full-stack development. My versatile background includes working with diverse companies, from small start-ups to large multinational corporations.

## Responses 1

Markdown supported · ⌘↵ to post

[Hayrullah Kar](https://hashnode.com/@magesheet)

[Oct 22](https://hashnode.com/posts/designing-a-reliable-integration-service-in-spring-boot-from-webhook-to-internal-apis/6ad91073f8e83c852bb7815d/comment/6ada4e7918f4724a63a007ec)

Rules 3 and 4 together leave one gap. The Resilience4j retry around createAccount fires on timeouts, but a timeout does not mean the account wasn't created. The downstream API may have finished the work and only the response got lost. Because the new ID and status are saved only after a successful response, the retry sends a second create and you get two accounts, which is exactly what the state machine was meant to prevent. Passing a stable idempotency key derived from the external ID (if the internal API supports one), or looking up by external reference before creating on a retry, closes it. Second, Resilience4j retries on every exception by default. Without retryExceptions or ignoreExceptions in the config, a 400 caused by bad data is also retried three times, which contradicts your Rule 4 table. A small one on Rule 2: when two duplicates arrive at the same time, the unique constraint makes the second save throw DataIntegrityViolationException. Catching it and still returning 202 stops the sender from retrying a request you already stored.
