Hello,
I'm building a microservice that integrates data from a SOAP webservice. For this I am using a scheduler that once per day searches for new data and writes to my mongodb database. Since the standard of service is to have one basis per service, and my service integrates data and serves that data for another service, how am I going to scale a microservice with those two things together? I will have a problem integrating the data, so I thought of two solutions:
1 - Divide my microservice into two: one will be responsible for integrating data with webservice SOAP and another will be responsible for serving this data, so I can scale this service. The problem is that it escapes the concept of microservice: a basis for service.
2 - Keep a single microservice and to solve the problem of scalability I could create a parameter to tell the other microservices not to run the scheduler, leaving only a microservice responsible for integrating the data. However, I do not know if this works and it seems like a bad solution.
What is the best solution? Is there another alternative?