I was confused that a micro-service (architecture) is just renaming SOA / Rest API / what-so-ever and connecting different components with a scalable message bus. And, now, you point out some great distinctions from those :) ty.
'''does not access common data repositories and stores its own data isolated'''
&
'''does its job and then pushes a new message on the queue with the results, it never talks via the network layer to anyone else for coordination or status'''
A web frontend to receive requests. Some requests are stored in a pub/sub message broker like Kafka / RabbitMQ. Some daemons would subscribe to the broker and do some work. Any processes would have HTTP REST API call / Thrift RPC to some other functional services. Each of those functional services and daemons are load balanced.