Building Robust Java Services: Unified Responses, Validation, and Idempotency

Unified Business Response Handling

According to Ant Financial Open Platform standards, a response should contain at least four fields: isSuccess (whether the call succeeded), data (response data), errorCode (error code), and errorMsg (error message). Implement a standard response using Spring AOP, JDK dynamic proxies, CGLIB proxies, or a common executor that wraps all requests with a unified try‑catch to prevent uncaught 500 errors.

Why Handle Errors at the Outermost Layer?

500 errors are fatal and provide no value to callers, whether they are front‑end applications or other business systems.

Standardized Error Codes

Define clear error codes such as PARAMETER_ERROR for invalid parameters, DATABASE_ERROR for database issues, and OUTER_SYSTEM_ERROR for external system failures. With consistent codes and messages, business teams can inform users accurately and set up alerts or automated operations.

2. Parameter Checking

Before executing business logic, validate input parameters to keep subsequent processing lightweight and follow the fast‑fail principle. Example checks include null checks, empty string checks, and collection emptiness checks.

if (null == m) { return; }

if (StringUtils.isEmpty(m)) { return; }

if (CollectionUtils.isEmpty(m)) { return; }

Additionally, you can verify JSON format safely:

try {
    JSON.parseObject(m);
    return true;
} catch (JSONExceptin e) {
    return false;
}

3. Retry Mechanism

For certain external system errors, implement multiple retries, assuming the external service is idempotent. This can improve success rates in unstable network conditions.

4. Idempotent Mechanism

Idempotency means that repeated identical requests should yield the same response until a final state is reached, regardless of previous partial successes or failures, preventing inconsistent intermediate states.

5. Lambda Usage

Using functional style can reduce exception occurrences, especially when processing collections. Example:

Optional.of(target)
    .getOrElse(new ArrayList())
    .filter(Object::NotNull)
    .forEach(() -> {});

This approach performs extensive checks and compatibility handling, lowering error probability, though debugging may become more challenging when many exceptions arise.