Get Ready for the Rise of Reactive Systems

IT architecture

1 - Get Ready for the Rise of Reactive SystemsGet Ready for the Rise of Reactive Systems

A new survey points to the rapid adoption of modern applications based on reactive system architectures.

2 - Importance of Reactive ComputingImportance of Reactive Computing

While 40% of the respondent described reactive computing as “totally important,” 43% said it is gaining momentum.

3 - Reactive Computing OutlookReactive Computing Outlook

Respondents believe that 70% of their companies—and 80% of the most successful enterprises–will have implemented reactive computing systems by 2018.

4 - Reactive Computing's Current Adoption RatesReactive Computing’s Current Adoption Rates

Only 13% said they have already adopted reactive computing; 26% said they plan to do so this year. More than four in 10 (41%) expect to adopt reactive computing by 2018.

5 - Drivers of Reactive Computing AdoptionDrivers of Reactive Computing Adoption

Scalability (31%), resilience (22%) and modernization (17%) are cited as the top three drivers.

6 - Obstacles to Reactive ComputingObstacles to Reactive Computing

The need to retrain existing IT staff (35%), organizational disruption (27%) and lack of senior-level management support (26%) were cited as the top three obstacles.

7 - Where Responsibility for Innovation LiesWhere Responsibility for Innovation Lies

Development teams (52%) are responsible for taking the first step in testing new technologies or architectural concepts, followed by architects (31%).

8 - Reactive Computing FocusReactive Computing Focus

29% said they are researching or actively learning about reactive computing. Another 19% said they are just starting to look into it.

9 - Reactive Computing Applications in ProductionReactive Computing Applications in Production

Only 18% said they have a reactive computing application in production, but another 16% said they are building one.

10 - Approaches to Reactive ComputingApproaches to Reactive Computing

41% said they will re-factor legacy systems, module by module; 24% plan to rewrite an existing development project to replace a legacy system; and 23% said they will “shave the existing stack” by replacing legacy bottlenecks or APIs.

Michael Vizard
Michael Vizard is a seasoned IT journalist, with nearly 30 years of experience writing and editing about enterprise IT issues. He is a contributor to publications including Programmableweb, IT Business Edge, CIOinsight, Channel Insider and UBM Tech. He formerly was editorial director for Ziff-Davis Enterprise, where he launched the company’s custom content division, and has also served as editor in chief for CRN and InfoWorld. He also has held editorial positions at PC Week, Computerworld and Digital Review.


Must Read