Hi Adekoyejo, I'm honestly not an expert on this topic but I think the hardest thing is testing interaction between multiple services.
As you mentioned each service (which is a self contained app) should have its own unit and functional testing but you still need to test service A talking with B.
I would research the literature on it. Check Martin Flower's website and these resources:
Setting up integration testing seems also a really good way to design and discuss service boundaries. How would the client consume service A and B? Do you need A and B to then call service C? Do you have all services behind a single gateway so that it's transparent to the client?
There's no easy way to do microservices, that's for sure.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Adekoyejo, I'm honestly not an expert on this topic but I think the hardest thing is testing interaction between multiple services.
As you mentioned each service (which is a self contained app) should have its own unit and functional testing but you still need to test service A talking with B.
I would research the literature on it. Check Martin Flower's website and these resources:
Pattern: Service Integration Contract Test
Spotify's Testing of Microservices
Setting up integration testing seems also a really good way to design and discuss service boundaries. How would the client consume service A and B? Do you need A and B to then call service C? Do you have all services behind a single gateway so that it's transparent to the client?
There's no easy way to do microservices, that's for sure.