microservices

问题 I\'m having a hard time choosing a decent/secure authentication strategy for a microservice architecture. The only SO post I found on the topic is this one: Single Sign-On in Microservice Architecture My idea here is to have in each service (eg. authentication, messaging, notification, profile etc.) a unique reference to each user (quite logically then his user_id ) and the possibility to get the current user\'s id if logged in. From my researches, I see there are two possible strategies: 1.

问题 Let\'s say we have a User, Wallet REST microservices and an API gateway that glues things together. When Bob registers on our website, our API gateway needs to create a user through the User microservice and a wallet through the Wallet microservice. Now here are a few scenarios where things could go wrong: User Bob creation fails: that\'s OK, we just return an error message to the Bob. We\'re using SQL transactions so no one ever saw Bob in the system. Everything\'s good :) User Bob is

问题 I am trying to create a microservice architecture using Lumen / Laravel Passport . I have a multiple dockerized services, which all run as an separate Lumen app container in different VMs: API Gateway service (integrated with Laravel Passport for authentication & request validation to further proceeding) Chat Service (service for messaging/chat rooms) News Service … (and many other services) All of this services has it’s own separated Redis/MySQL databases e.t.c. In monolithic application,

问题 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

问题 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