going reactive 2016 - report preview

25
GOING REACTIVE 2016 HOW MICROSERVICES AND FAST DATA ARE DRIVING MAINSTREAM ADOPTION OF REACTIVE SYSTEMS

Upload: typesafeinc

Post on 03-Mar-2017

6.132 views

Category:

Technology


2 download

TRANSCRIPT

Page 1: Going Reactive 2016 - report preview

GOING REACTIVE 2016HOW MICROSERVICES AND FAST DATA ARE DRIVING MAINSTREAM ADOPTION OF REACTIVE SYSTEMS

Page 2: Going Reactive 2016 - report preview

2

28 industries represented

62 tools & technologies included

3060 total respondents

2O questions

2% margin of error at a 95%

confidence interval

Page 3: Going Reactive 2016 - report preview

3

CURRENT JOB ROLE

24% Architect

10% Management/CIO/CTO

4% Other3% Dev Ops

59% Developer

Page 4: Going Reactive 2016 - report preview

4

INDUSTRY OF OPERATION

4% Media

6% Telecommunications5% Government/Military

6% Business Services

7% Consulting8% Online Services

13% Financial Services

21% Technology

Page 5: Going Reactive 2016 - report preview

REACTIVE ADOPTION TRENDS

Experiences and predictions about Going Reactive

Page 6: Going Reactive 2016 - report preview

6

elastic resilient

message-driven

responsive

THE FOUR TENETS OF REACTIVE SYSTEMS

Page 7: Going Reactive 2016 - report preview

7

PERCEPTIONS OF THE GOING REACTIVE TREND

43%

Gaining momentum,

should start looking

into it soon

12%

Enjoying a lot of buzz,

but that’s probably it

40%

Totally important,

something we needed

yesterday

5%

ZOMG,

not Reactive again!

Page 8: Going Reactive 2016 - report preview

8

PREDICTIONS FOR REACTIVE SYSTEMS ADOPTION

13%14%

Their organizationMost successful enterprises

Already adopted By 2016 By 2018 Later than 2018

26%

24%

41%

31%

20%

31%

Page 9: Going Reactive 2016 - report preview

9

PRIMARY DRIVERS OF GOING REACTIVE

31%31%

ScalabilityScalability

22%22%

ResilienceResilience

17%17%ModernizationModernization

16%16%

VelocityVelocity

15%15%EfficiencyEfficiency

Page 10: Going Reactive 2016 - report preview

10

Just starting to lookinto the topic

Not applicable to me

Already learningor doing research

Building a prototype

Running a productionapplication

Developing aproduction application

4%

19%

29%14%

18%

16%

34%

Power

users

43%

Active

starters

19%

Entry

level

GOING REACTIVE PHASE OF JOURNEY

Page 11: Going Reactive 2016 - report preview

11

PREDICTIONS AND ACTIONS TAKEN TOWARDS GOING REACTIVE

Say that Reactive demands attention83%

Already researching and prototyping43%

Building and deploying production systems34%

Expect enterprise adoption by 201880%

Page 12: Going Reactive 2016 - report preview

MICROSERVICES AND REACTIVE SYSTEMS

The embrace of Microservices and related tools in Reactive

Page 13: Going Reactive 2016 - report preview

13Just Learning Building & DeployingResearching & Prototyping

16%

28%

50%

MICROSERVICES ADOPTION BY PHASE OF JOURNEY

Page 14: Going Reactive 2016 - report preview

14

USE OF JAVA AND SCALA WITH MICROSERVICES

30% Java 7 or lower

Java 8

64% Scala

61%

41%

52%

50%

- - - - ------ = average for all respondents

Page 15: Going Reactive 2016 - report preview

15

PREFERRED OPS/INFRA/DEVOPS TECHNOLOGIES WITH MICROSERVICES

29% Not Microservices-based

34% All respondents

47% Microservices-based architectures

Uses Docker

3% Not Microservices-based

7% All respondents

13% Microservices-based architectures

Uses Mesos

34% Not Microservices-based

40% All respondents

52% Microservices-based architectures

Uses Amazon EC2

Page 16: Going Reactive 2016 - report preview

16

12% Not Microservices-based

18% All respondents

28% Microservices-based architectures

Uses Cassandra

11% Not Microservices-based

17% All respondents

27% Microservices-based architectures

Uses Kafka

17% Not Microservices-based

22% All respondents

30% Microservices-based architectures

Uses Spark

PREFERRED BIG [FAST] DATA TECHNOLOGIES WITH MICROSERVICES

Page 17: Going Reactive 2016 - report preview

17

34% Not Microservices-based

All respondents

59% Microservices-based architectures

43%

Uses Akka

24% Not Microservices-based

30% All respondents

40% Microservices-based architectures

Uses Play

Use of Spring and Play with Microservices

PREFERRED DEVELOPER TECHNOLOGIES WITH MICROSERVICES

Page 18: Going Reactive 2016 - report preview

FAST DATA AND REACTIVE SYSTEMS

The embrace of data in motion and related tools in Reactive systems

Page 19: Going Reactive 2016 - report preview

19

USAGE OF SPARK ALONG STAGE OF JOURNEY

Just Learning13%

Building & Deploying28%

Researching & Prototyping21%

Page 20: Going Reactive 2016 - report preview

20

MICROSERVICES AND SPARK

MSA usingSpark

30%Spark users

with MSA

46%

Page 21: Going Reactive 2016 - report preview

21

USE OF JAVA AND SCALA WITH APACHE SPARK

34% Java 7 or lower

58% Java 8

76% Scala

41%

52%

50%

- - - - ------ = average for all respondents

Page 22: Going Reactive 2016 - report preview

22

43%

64%

Average Spark users

Akka Amazon EC2 Cassandra HadoopDocker

40%

55%

18%

44%

34%

52%

16%

46%

MesosKafka

17%

49%

7%

22%

INCREASED TOOL USAGE AMONG APACHE SPARK USERS

Page 23: Going Reactive 2016 - report preview

CONCLUSIONS AND TL;DR

Three conclusions nicely wrappedup for busy readers

Page 24: Going Reactive 2016 - report preview

24

CONCLUSIONS (TL;DR)For those of you too busy to internalize everything in this report at

once, we can narrow down the final points into three main conclusions:

Reactive system adoption is going mainstream

Reactive adoption is being driven by two key technology trends: Microservices and Fast Data

Microservices and Fast Data users are rallying around a preferred group of tools and technologies

1.

2.

3.

43% 59% 64%

40% 52% 55%

18% 28% 44%

34% 47% 52%

17% 27% 49%

7% 13% 22%

30% 40% 38%

22% 30% -

SPARKUSERS

ALLRESPONDENTS

MICROSERVICES USERS

Page 25: Going Reactive 2016 - report preview

25

ADDITIONAL RESOURCES

Typesafe (Twitter: @Typesafe) is dedicated to helping developers build Reactive applications on the JVM. Backed by Greylock Partners, Shasta Ventures, Bain Capital Ventures and Juniper Networks, Typesafe is headquartered in San Francisco with offices in Atlanta, Switzerland and Sweden. To start building Reactive applications today, learn about Reactive Platform.

© 2015 Typesafe

Reactive Streams, Akka Streams and Akka HTTP

DOWNLOAD

Microservices inProduction

DOWNLOAD

Fast Data: Big Data Evolved

DOWNLOAD