Timeline for API Gateway (REST) + Event-Driven Microservices
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2016 at 10:40 | comment | added | Andy Hunt | It depends on where you're performing the action. If you're inside the user system, you can do all your validation, writing to data store there, then publish the event. Otherwise, I see it as perfectly acceptable to perform a standard HTTP request to the /users/ endpoint, and allow that system to publish its event if it succeeded, and respond to the request with the new entity | |
| Jun 2, 2016 at 10:09 | comment | added | Tony E. Stark | I mean, how do I report back to REST clients errors which occur when handling the UserCreated event (for example, duplicate username or email or database outage). | |
| Jun 2, 2016 at 9:15 | comment | added | Tony E. Stark | I understand. But what about error handling (and reporting) to the clients in this scenario? | |
| Jun 2, 2016 at 7:49 | history | answered | Andy Hunt | CC BY-SA 3.0 |