There has been a lot of buzz about reactive systems over the past couple of years.

Along with the buzz comes the collection of relevant keyword salads like reactive streams, reactive extensions, reactive programming, functional reactive programming, etc.
If you’ve been in the technology industry long enough, you’ve seen the cyclical ups and downs of buzzwords and acronyms from time to time.
So, is all of that another soon-to-be-dated hype?I’ve heard software engineers dismissing reactive systems as nothing more than an alias for asynchronous event-based systems, much like the way some dismiss microservices as SOA (service oriented architecture) less ESB (enterprise service bus). While technology buzzwords with reinvented meaning do oftentimes pop up, I see enough distinctive traits in reactive systems to think that the name isn’t simply another alias.To read this article in full or to leave a comment, please click here

Leave a Reply