microservices

Maybe this is a strange question (I'm new with Microservices). But I'm looking for some info on how proceed with this. Does not need to be Spring specific, but that's the framework I'm using at the moment. Example: Lets say we have two Microservices a) http://myurlfortesting.com:8085/api/rest/serviceone b) http://myurlfortesting.com:8090/api/rest/servicetwo and we have setup Spring Zuul (acting as the API Gateway) with the following rules that forward the incoming calls: /rest/one -> http://myurlfortesting.com:8085/api/rest/serviceone /rest/two -> http://myurlfortesting.com:8090/api/rest

I have two (but let's image more) micro-services (API) which need to be aware of authenticated user. Ideally I would simple like to resume their sessions. All micro-services are using same storage for sessions: redis. All API calls will have Cookie header, so all services will be able to resume sessions based on that cookie. I have successfully implemented this via PHP $_SESSIONs. Now the question: how would you go about implementing this with Laravel/Lumen? The accepted answer is outdated. I answered and explained a bit how to properly do it in my answer on this question I also posted what is

We are using microservices approach to build our product. We are using some projects which each uses docker-compose to run. The problem is that in development environment, if we want to change codes in multiple projects and test developed codes, we must run projects separately and link them together manually. Now we want to create a development kit which clones projects and runs them together and handles links. Can docker-compose handle multiple docker-compose file? If not is there any sufficient tool to do that for us? Or is there any recommended approach for our goal? EDIT: For example we

I have read an article " Microservices " by Martin Fowler and find it difficult to understand smart endpoint s and dumb pipes . Please explain these terms, examples are welcome. I didn’t read the article, so I can only speculate what he can mean exactly, but as he gives ESB as an example against microservices and ZeroMQ as an example for micro services I hope my speculation will be pretty exact: One of the ideas of Unix (and Linux) is to build small independent applications and connect them via pipes. The probably most common set of two command which I’m using is ps and grep like this: ps aux

I go into microservices architecture based on docker and I have 3 microservices, which together create one product for example "CRM system". Now I want my client to be able to upgrade his product, whenever he wants to. I have 3 different versions of my microservices, which one should client see? I guess product version should be independent of microservices, because copying one of the microservices version would make me go into more trouble than having no version at all. So is there any pattern, idea to handle such situation? The only thing that comes to my mind is to have another repository

I need to implement pipeline if Service Fabric's Reliable Services, and I need some guidelines about what of these approaches is preferable from the viewpoint of reliability simplicity and simple good design: I have been investigating this topic a lot as well (to be applied to my work for NServiceBus and MessageHandler ) and would like to provide my thoughts on the matter. However I haven't determined what the best model is yet. If you disregard the practical implementation with ServiceFabric I would categorize the proposed approach in the following order when it comes to reliability: C) The