SO, forgot to add question (4) to my "followup on (Reactive) Microservices Design"
What's the essential Schema design approach for solving the problem of associating data between Services? i.e. Between Customer Order Service and Seller Fulfillment Service? OLD SCHOOL: Foreign Key for Order ID on Fulfillment to handle 1:N Order:Fulfillments NEW SCHOOL(guessing): Denormalized Order-Fulfillment data records for Fulfillment Service; and dependent on Order Version? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
