适配Java的Job/Work Queue Server选型：支持HTTP任务重试与Form参数

Absolutely, there are several robust options in the Java ecosystem that check all your boxes. Below are the most practical choices, tailored to your needs:

JobRunr #

This is one of the most straightforward, out-of-the-box solutions for Java-based job queuing:

• Java Integration: Supports both a native SDK (easy to plug into any Java/Spring app) and a REST API for submitting jobs.
• HTTP POST with Form Params: You can directly define tasks that send form-encoded POST requests to external URLs within your job logic.
• Retry for Non-200 Responses: Built-in retry policy configuration lets you specify the number of retries, delay intervals (including exponential backoff), and which errors (like 400/404) trigger retries. Just throw a custom exception when a non-200 response is received, and JobRunr handles the rest.
• Bonus: Includes a web dashboard to monitor job status, retry history, and failures.

Here's a quick code snippet to illustrate submitting a form POST job with retry:

// Initialize JobRunr (typically done in your Spring config or main class)
JobScheduler jobScheduler = JobRunr.configure()
        .useStorageProvider(new InMemoryStorageProvider()) // Switch to Redis/SQL for production
        .withRetryPolicy(RetryPolicy.builder()
                .withMaxNumberOfRetries(3) // Retry up to 3 times
                .withDelay(Duration.ofSeconds(5)) // Wait 5s between retries
                .build())
        .initialize();

// Submit a job that sends a form-encoded POST request
jobScheduler.enqueue(() -> {
    HttpClient client = HttpClient.newHttpClient();
    String formData = "username=test&email=test@example.com";
    HttpRequest request = HttpRequest.newBuilder()
            .uri(URI.create("https://your-external-url.com/endpoint"))
            .header("Content-Type", "application/x-www-form-urlencoded")
            .POST(HttpRequest.BodyPublishers.ofString(formData))
            .build();

    HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString());
    if (response.statusCode() != 200) {
        // Trigger retry by throwing an exception
        throw new RuntimeException("Received non-200 status: " + response.statusCode());
    }
});

Spring Cloud Task + Spring Cloud Stream #

If you're already working within the Spring ecosystem, this combination is a great fit:

• Java Integration: Seamless SDK integration with Spring Boot apps; you can also expose a custom REST API to accept job submissions.
• HTTP POST Handling: Wrap your form-encoded POST logic into a Spring Task, then send it to a message queue (like RabbitMQ or Kafka) via Spring Cloud Stream.
• Retry Logic: Use Spring Retry to define retry rules for non-200 responses—you can configure retry counts, backoff strategies, and even skip retries for specific status codes (e.g., permanent 404s).
• Scalability: Works well for distributed systems, as you can scale task workers independently.

Apache Camel #

For more complex integration scenarios, Apache Camel offers powerful routing and queuing capabilities:

• Java Integration: Use Camel's Java DSL to define job routes, or expose REST endpoints via Camel's REST component to accept job submissions.
• HTTP POST & Retries: Camel has built-in components for HTTP calls and retry policies. You can configure routes that queue form-encoded POST requests, send them to external URLs, and retry on non-200 responses with custom rules.
• Flexibility: Supports multiple queue backends (ActiveMQ, RabbitMQ, etc.) and integrates with almost any Java framework.

内容的提问来源于stack exchange，提问作者quarks