3 ms·
I may be getting this wrong, but I was under the impression that microservices are about having many small services as in a service bus architecture. I don't kn
by cm3 10y ago
I may be getting this wrong, but I was under the impression that microservices are about having many small services as in a service bus architecture. I don't know how the author came to believe it's about short response times.
EDIT: Reading the responses, I should clarify: The question is if a microservice needs to be be fast to respond to be considered a microservice, or if both types are called micro based solely on the fact that they are limited-purpose small services, together building a greater construct. I would say kinda-synchronous fast responding services are just as micro as very-asynchronous slow responding but still limited API services are.
- chrishacken 10y agoNor do I. Micro services are built around being able to be scaled and manipulated without having those changes break your entire application.
- the_mitsuhiko 10y agoMicroservices are SOA and there are two ways in which that typically happens: slow offline processing with many different workers. That's not really an issue and something that is a well understood problem. The second however is offloading work to different processes while something is waiting for a result and it wants it quick (a web request). In the latter case it's absolutely important that your services reply quickly.
- akerro 10y agoI'll return answer to your question in a week. Hope you will be still interested to hear it.
- detaro 10y ago(I assume) it is not about short response times, but short response times are necessary if you split your work in many (assumed partially serial) requests to small services and still want acceptable overall response time.