如何在Eureka/Config/Zuul环境下用REST API完成Eureka应用驼峰式注册？

Hey there, let's break down exactly how to register your DemoClient with Eureka using its REST API (focused on camel-case naming requirements) and cover all critical notes to avoid pitfalls.

1. Quick Test with CURL #

This is the fastest way to validate the registration flow. Send a POST request to the Eureka API endpoint with a properly formatted JSON body (strict camel-case fields required):

curl -X POST \
  http://localhost:8761/eureka/apps/DemoClient \
  -H 'Content-Type: application/json' \
  -d '{
    "instance": {
      "instanceId": "localhost:DemoClient58181",
      "hostName": "localhost",
      "app": "DemoClient",
      "ipAddr": "localhost",
      "vipAddress": "DemoClient",
      "secureVipAddress": "DemoClient",
      "status": "UP",
      "port": {"$": "58181", "@enabled": "true"},
      "healthCheckUrl": "http://localhost:58181/actuator/health",
      "statusPageUrl": "http://localhost:58181/actuator/info",
      "homePageUrl": "http://localhost:58181/",
      "dataCenterInfo": {
        "@class": "com.netflix.appinfo.InstanceInfo$DefaultDataCenterInfo",
        "name": "MyOwn"
      }
    }
  }'

• A 204 No Content response means registration succeeded.
• The -H 'Content-Type: application/json' header is mandatory—Eureka won't parse unmarked JSON bodies.

2. Using API Tools (Postman/Insomnia) #

For a more visual approach:

• Create a new POST request with URL: http://localhost:8761/eureka/apps/DemoClient
• Add the header Content-Type: application/json
• Switch to the Body tab, select raw > JSON, then paste the full request body from the CURL example above
• Click "Send"—you'll get a 204 response on success.

3. Programmatic Registration (Java RestTemplate Example) #

If you need to automate registration within an application, use RestTemplate (or WebClient for reactive apps):

import org.springframework.web.client.RestTemplate;

public class EurekaManualRegistration {
    public static void main(String[] args) {
        String eurekaApiUrl = "http://localhost:8761/eureka/apps/DemoClient";
        RestTemplate restTemplate = new RestTemplate();

        // Full instance JSON (you can also map to POJOs for type safety)
        String instancePayload = "{\"instance\": {\"instanceId\":\"localhost:DemoClient58181\",\"hostName\": \"localhost\",\"app\": \"DemoClient\",\"ipAddr\": \"localhost\",\"vipAddress\": \"DemoClient\",\"secureVipAddress\": \"DemoClient\",\"status\": \"UP\",\"port\": {\"$\": \"58181\",\"@enabled\": \"true\"},\"healthCheckUrl\": \"http://localhost:58181/actuator/health\",\"statusPageUrl\": \"http://localhost:58181/actuator/info\",\"homePageUrl\": \"http://localhost:58181/\",\"dataCenterInfo\": {\"@class\": \"com.netflix.appinfo.InstanceInfo$DefaultDataCenterInfo\",\"name\": \"MyOwn\"}}}";

        restTemplate.postForObject(eurekaApiUrl, instancePayload, String.class);
        System.out.println("DemoClient registered successfully via REST API!");
    }
}

Note: For production code, define POJOs matching Eureka's InstanceInfo structure (with camel-case fields) instead of raw JSON strings—it's more maintainable.

• Strict Camel-Case Enforcement: Eureka's REST API is case-sensitive for field names. Use instanceId, hostName, not instance_id or hostname—incorrect casing will cause silent failures or malformed instance records.
• Complete Request Body: Don't omit required fields like healthCheckUrl, statusPageUrl, or dataCenterInfo. Eureka uses these to track instance health and metadata.
• Unique instanceId: Each registered instance must have a unique instanceId—duplicates will overwrite existing registrations.
• Authentication (If Enabled): If your Eureka Server uses Spring Security, append credentials to the URL: http://username:password@localhost:8761/eureka/apps/DemoClient.
• Heartbeat Maintenance: Manual registrations don't auto-send heartbeats. You'll need to implement periodic PUT requests to http://localhost:8761/eureka/apps/DemoClient/localhost:DemoClient58181 (the instance ID endpoint) to keep the instance marked UP—otherwise Eureka will mark it DOWN after 90 seconds of inactivity.
• Port Field Format: The port field uses a nested object with $ for the port number and @enabled for status—don't change this structure, or Eureka won't recognize the port.

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