(if you can t read this, move closer!) The high-performance protocol construction toolkit. Peter Royal

Transcription

1 (if you can t read this, move closer!) Apache The high-performance protocol construction toolkit. Peter Royal <proyal@apache.org> Originally presented at ApacheCon Europe 2007 in Amsterdam

2 Hi, I m Peter

3 MINA hacker since Fall 2005

4 Radar Networks

5 San Francisco

6 Apache Member

7 What is MINA?

8 MINA?

9 Multipurpose Infrastructure Networked Applications

10 Built on Java NIO

11 Non-Blocking

12 Asynchronous

13 Event-Driven (SEDA!)

14 Multiple Transports (framework is really agnostic)

15 TCP

16 UDP (being re-written for 2.0)

17 In-VM (great for testing)

18 RS-232 (under development)

19 Smartly Designed

20 Follows Inversion of Control Pattern (plays nicely with PicoContainer, Spring, etc)

21 Separation of Concerns

22 Wire Protocol Application Logic Rather than this...

23 Wire Protocol Application Logic Concerns are Separated

24 Stable and Production- Ready v1.0 released Fall 2006 v1.1 released April 2007 Same API as v1.0 but uses Java 5 Concurrency primitives v2.0 this year API simplification based on lessons learned

25 Many Users

26 Apache Directory LDAPv3, NTP, DNS, DHCP and Kerberos

27 AsyncWeb (joining Apache very soon though!) HTTP/HTTPS

28 Apache (incubating) Qpid Advanced Messaging Queuing Protocol (AMQP) (from Wall Street!)

29 QuickFIX/J Financial Information exchange (FIX)

30 Openfire products/openfire/ XMPP

31 red5 RTMP (talk to Flash player)

32 ...and more! (maybe you, next time!)

33 Key Concepts

34 ByteBuffer Core NIO construct MINA version that wraps and provides additional convenience methods auto-expanding, string encoding MINA gives control... allocate from the Heap or Stack optional Pooling (in v2, will be non-pooled and heap-only, as it provides the best performance)

35 Future Represents a function call that completes asynchronously Provides blocking functions to retrieve the result MINA allows callbacks to be invoked upon completion, so invoking thread can fire and forget (unlike the Java 5 Future)

36 Writes IoHandler IoProcessor IoService Reads

37 Writes IoHandler IoProcessor IoService Reads Two Versions

38 Writes IoHandler IoProcessor IoService Reads IoAcceptor act as server single thread for new connections

39 Writes IoHandler IoProcessor IoService Reads IoConnector act as client

40 Writes IoHandler IoProcessor IoService Reads Connection instance is an IoSession

41 Writes IoHandler IoProcessor IoService Reads Handles reads and writes

42 Writes IoHandler IoProcessor IoService Reads Instance count scales with CPU/Load

43 Writes IoHandler IoProcessor IoService Reads Session fixed to an Instance (under review for v2)

44 Writes IoHandler IoProcessor IoService Reads Chain of s

45 Writes IoHandler IoProcessor IoService Reads Per Connection

46 Writes IoHandler IoProcessor IoService Reads Reusable

47 Writes IoHandler IoProcessor IoService Reads Hot Deployable

48 Writes IoHandler IoProcessor IoService Reads Filter all events Read / Write / Idle / etc

49 Writes IoHandler IoProcessor IoService Reads Application Logic Lives Here

50 Large Library of s

51 Protocol Conversion Framework to plug in your own codecs to handle conversion to/from a ByteBuffer Existing codecs Text-based Java Serialization

52 Blacklist

53 Logging (great for debugging!)

54 SSL / TLS

55 Compression

56 Read Throttling (we re working on a general solution for writes)

57 Thread Models (a necessary evil)

58 single threaded

59 One IoProcessor Thread

60 Scalability sucks

61 Add more IoProcessor Threads (at least one per CPU core)

62 Lowest latency Scales nicely (connection latency to be addressed in v2)

63 multi threaded

64 use ExecutorFilter

65 IoProcessor threads only do reads & writes (the intent)

66 Filters execute on a different thread. (filter location is key!)

67 Work for a session is serialized (queued per session)

68 Work is delegated to an Executor (generally a java.util.concurrent.threadpoolexecutor)

69 Size thread pool to active session count (too much in queue == OOM! Use the Read Throttle filter)

70 recommended application pattern use ExecutorFilter as first in chain unless you need really low latency use ProtocolCodecFilter convert the wire protocol into a Java representation put application logic into an IoHandler store state in the IoSession minimum of Java 5 java.util.concurrent rocks!

71 Example Time!

72 Everybody loves a Haiku

73 This is our Haiku validator

74 Simple Protocol Connect Send 3 lines of text Receive HAIKU! or NOT A HAIKU: (plus a little reason why not)

75 ProtocolCodecFilter + TextLineCodecFactory Bytes to Java String s. For free!

76 ToHaiku Three String s to a Haiku

77 Filter is very testable (mock objects rock!)

78 IoHandler is very simple Validate Haiku, send result

79 Also very testable

80 Very easy to hook it all up

81 Questions?

82 Thank You!

83