3
Hello,
I’m building a microservice that integrates data from a SOAP webservice. For this I am using a scheduler that once a day searches new data and writes in my base mongodb. Since the standard of microservice is to have one base 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’m going to have a problem with data integration, so I thought of two solutions:
1 - Divide my microservice into two: one will be responsible for integrating data with the SOAP webservice and the other will be responsible for serving this data, so I can scale this service. The problem is that this escapes the concept of microservice: one basis per service.
2 - Maintain a single microservice and to solve the scalability problem I could create a parameter to tell other Microservices not to run the scheduler, leaving only one microservice responsible for integrating the data. However, I don’t know if this works and it seems to me a bad solution.
What is the best solution? There is another alternative?