Is there a strategy or pattern to pass common data inside a microservice architecture? -


i part of team breaking large monolithic web service in e-commerce sector. have identified components isolated enough , have started breaking out success.

i wondering if there known pattern of trying keep common data between of services. example, edge process gathers few things (maybe basic user information, mobile browser, etc..) , services downstream take advantage of data or maybe augment of data.

now, wiser keep data , pass service service per request, or there pattern of trying put temporary storage , having available of services going touch on request.

is session service answer since seems common dependency , have scale such? or pass data service service , if request chain has have added go touch points needed?

data see needing passed around:

  • user identification.
  • browser type identification original request.
  • what kind of tests original requester may in.


Comments

Popular posts from this blog

node.js - Node js - Trying to send POST request, but it is not loading javascript content -

javascript - Replicate keyboard event with html button -

javascript - Web audio api 5.1 surround example not working in firefox -