Dr Mark Little Red Hat, Inc.

Transcription

1 Enterprise Middleware and the Internet of Things! A Call to ARMs Dr Mark Little Red Hat, Inc. 1

2 Overview Challenges for enterprise middleware Changing realities for Java Applications and their requirements What can Java do to help? Java and IoT - the JBoss examples Building on MBed, Pi or Android Where next? 2

3 Challenges Cloud Public, private and hybrid DevOps Mobile Ubiquitous computing IoT Big Data/NoSQL Event-driven/data-driven/reactive/asynchronous Microservices Docker Container-less development 3

4 30 years ago 16K was considered a lot of memory 140K floppy disks were the standard 10 mbps ethernet was decadent 8 bit 6502 processor was king for personal computing Wireless was what people listened to when there was nothing on TV 4

5 Today 2 Gig memory is standard on smart phones, 64Gig storage 256Gig USB sticks are becoming the norm 100Gig ethernet at work and 30mbps to the home 64 bit quad core processors in laptops, 2GHz ARM in phones WiFi throughout many cities 5

6 Where is IoT today? 1. Transportation 2. Smart Service Sector/Retail Payments from devices, wallets, conversion of bitcoins to currency, etc. 3. Smart Grid/City/Utilities Smart sensors to centralised backend services, provisioning, etc.) 4. Smart Supply Chain/Manufacturing 5. Medical 6. Environmental 7. Home Automation/Smart Home Most popular topic among developers 8. Wearables Google glass, fitbit, samsung watches, proteus, etc. 9. Defence Localised mesh network 6

7 7

8 Java not up to the task? JavaScript and Node.js (client and server) Go[lang] (Cloud, Docker, Kubernetes) Erlang (enterprise messaging) Dart (client and server) Swift (mobile) Objective-C (mobile) Python (Cloud, OpenStack) C/C++ (client/edge-devices and server) 8

9 9

10 Why should we be interested? Types of IoT application increasing in complexity Online purchases Distributed peer-to-peer interactions More requirements becoming a necessity Security and identity - cloud breaches bad enough! High performance, low latency, reliable messaging Database updates with transactions Workflows as inter-app interactions increase 10

11 11

12 Familiar requirements? Many commonalities with Java middleware Messaging Transactions Security Non-JVM languages are a necessity, e.g., clients on thin (edge?) devices But we cannot afford to re-implement the world Java has a significant role to play 12

13 Richard Hamming, 1968 Turing speech Whereas Newton could say, "If I have seen a little farther than others, it is because I have stood on the shoulders of giants," I am forced to say, "Today we stand on each other's feet." Perhaps the central problem we face in all of computer science is how we are to get to the situation where we build on top of the work of others rather than redoing so much of it in a trivially different way. 13

14 Examples of JBoss/Red Hat and IoT Why spend the time? Non-traditional enterprise deployments These demands are coming Focus on MBed, Pi, Mobile (Android) Not just edge devices Looking at core capabilities initially Well maybe a bit of fun too Narayana, Arquillian, Vert.x, ActiveMQ, Infinispan, Fabric, jbpm, 14

15 Typical deployments Build Devices / Clients Integration! Data Process Messages Applications Web Services Databases Data Center Enterprise Applications Management/Provisioning 15

16 Microservices? (It s SOA!) 16

17 Services, VMs and JVMs 2.0 Machine A Machine B Machine C Service JVM VM Java EE services (in blue) split across machines, VMs and JVMs Service instance may abstract more cloud instances 17

18 ActiveMQ In Space! 18

19 Apollo and the God Particle 19

20 OSGi and IoT OSGi is central to Java and IoT OSGi is part of the Home Gateway Initiative specifications Currently active RFCs are: RFC 192: ZigBee Device Service Specification RFC 196: Device Abstraction Layer RFC 199: EnOcean Device Service Specification RFC 200: Resource Management RFC 202: USB Device Category RFC 209: Network Interface Information Service 20

21 21

22 22

23 23

24 24

25 MongoDB!!!!!!! 25

26 Java in 2000 Java in 2015 J2SE 1.3 J2EE 1.2 to 1.3 Typical laptop configuration o 1 GHz Pentium III with 512 Meg and 20 Gig disk o! Sufficient to run full J2EE stack Limited mobile devices o o HP Jornada 720, 206MHz StrongArm SA bit processor, 32 MB SDRAM, Windows CE! Sufficient to run some components of J2EE Java SE 8 Java EE 6/7 Typical laptop configuration o 2.5 GHz Quad Core i7 with 16 Gig and 256 Gig SSD! o Sufficient to run full EE6 stack (on several different OS concurrently) Smartphones o Samsung Galaxy S5, Quad Core 2.5 GHz Krait 400 o! Sufficient to run many components of EE6

27 27

28 Transactional Android 28

29 Code changes For Raspberry Pi? It s standard Java No code changes Just add a little more patience For Android? No StAX by default Classloading is *very* different Remember to use core-library to get javax Some pre-jdk 1.6 compilation issues 29

30 Conclusions IoT applications beginning to need capabilities normally associated with enterprises Trillions of sensors Billions of phones Cloud needs intelligent participants Data on the inside vs data on the outside IoT, Cloud, microservices represent an opportunity for Java 30

31 31

32 32