microservices

What is the standard pattern of orchestrating microservices? If a microservice only knows about its own domain, but there is a flow of data that requires that multiple services interact in some manner, what's the way to go about it? Let's say we have something like this: Invoicing Shipment And for the sake of the argument, let's say that once an an order has been shipped, the invoice should be created. Somewhere, someone presses a button in a GUI, "I'm done, let's do this!" In a classic monolith service architecture, I'd say that there is either an ESB handling this, or the Shipment service

I have a scenario in Zuul where the service that the URL is routed too might be down . So the reponse body gets thrown with 500 HTTP Status and ZuulException in the JSON body response. { "timestamp": 1459973637928, "status": 500, "error": "Internal Server Error", "exception": "com.netflix.zuul.exception.ZuulException", "message": "Forwarding error" } All I want to do is to customise or remove the JSON response and maybe change the HTTP status Code. I tried to create a exception Handler with @ControllerAdvice but the exception is not grabbed by the handler. UPDATES: So I extended the Zuul

Reading this doc it says "You must initially deploy a version of your app to the default service before you can create and deploy subsequent services." I don't understand this because I thought the GAE microservices were separate things as in: But it seems this is not an accurate depiction of how GAE microservices work? Is there like a master controller "default" service that sets top level config or does some kind of routing? If I'm just running a bunch of non web apps (meaning apps that wil run on a scheduled and process data) and a frontend "app" for accepting web requests isn't necessary