We've stuck with designing two services. In fact, these two services have been splitted since traffic issues, so they were one before.
I mean, our platform is consumed by two sort of clients: other services and UI clients (web, desktop and mobile).
- Services are using a very short number of exposed endpoints (
- Althought they are using those methods they generates more traffic than clients.
- Clients are using a very large number of exposed endpoints.
- Nevertheless, they are not generating so many traffic.
So, they are sharing code (since they are accessing to the same database), but as far I've been to figure out microservices has no to share base code.
We believe something is wrong using this approach.
I don't know if I've explained so well.
Which would be the keys in order to solve this kind of microservices architecture issues? Is "traffic issue" a key enought in order to split a service?