Before we dive into reactive microservices, let's see what the word reactive means. There are certain fundamental attributes that a piece of software must possess, in order to be considered reactive. These attributes are responsiveness, resilience, elasticity, autonomy, and, above all, being message-driven. We'll discuss these attributes in detail, and we'll look at how they can make microservices stronger candidates, for most enterprise requirements.
Understanding reactive microservices
Responsiveness
It wasn't long ago when one of the key requirements of business sponsors, discussed in requirement gathering sessions, was a guaranteed response time of a few seconds. For example, I remember when we...