The document discusses real-time web applications and some of the challenges and solutions in building them. Some of the key challenges mentioned are providing real-time services, supporting many concurrent users, handling big data and scalability issues, and security concerns. Potential solutions discussed include using non-blocking I/O with event-based frameworks like Node.js, storing data in NoSQL databases like Redis for flexibility and performance, and implementing throttling to prevent flooding attacks and limit request rates. Node.js is highlighted as a good option due to its asynchronous non-blocking model, speed with Google's V8 JavaScript engine, and large ecosystem of packages.

1. TECHNOLOGY TRENDS
Realtime web application

2. TECHNOLOGY TRENDS
Realtime web application
Muqorrobien Marufi
r@nosql.asia

3. PAST
Searching....

4. NOW?

6. Subscribing

7. Subscribing

8. Subscribing

9. Subscribing

10. Subscribing

11. Subscribing

13. PUBSUB
PUBLISHER-SUBSCRIBER

14. PUBSUB
PUBLISHER-SUBSCRIBER
Information
Provider

15. PUBSUB
PUBLISHER-SUBSCRIBER
Information Information
Provider Consumer

16. PUBSUB
PUBLISHER-SUBSCRIBER
PUBSUB
MIDDLEWARE
Information Information
Provider Consumer

17. PUBSUB
PUBLISHER-SUBSCRIBER
PUBSUB
MIDDLEWARE
Publish
Information Information
Provider Consumer

18. PUBSUB
PUBLISHER-SUBSCRIBER
PUBSUB
MIDDLEWARE
Publish
Subscribe
Information Information
Provider Consumer

19. PUBSUB
PUBLISHER-SUBSCRIBER
PUBSUB
MIDDLEWARE
Publish
Receive
Subscribe
Information Information
Provider Consumer

21. THE PROBLEM IS...

22. THE CHALLENGE IS...

23. CHALLENGE

24. CHALLENGE
1.Realtime service.

25. CHALLENGE
1.Realtime service.
2.Concurrent user.

26. CHALLENGE
1.Realtime service.
2.Concurrent user.
3.Big Data & Scalability.

27. CHALLENGE
1.Realtime service.
2.Concurrent user.
3.Big Data & Scalability.
4.Security.

29. SOLUTIONS

30. 1. NON BLOCKING I/O

31. 1. NON BLOCKING I/O
MULTI THREADED IO LOOP / EVENT BASED

32. 1. NON BLOCKING I/O
MULTI THREADED IO LOOP / EVENT BASED

33. 1. NON BLOCKING I/O
MULTI THREADED IO LOOP / EVENT BASED

34. 1. NON BLOCKING I/O

35. 1. NON BLOCKING I/O
• Event-based I/O.

36. 1. NON BLOCKING I/O
• Event-based I/O.
• Tornado, Twisted, Gevent (Python).

37. 1. NON BLOCKING I/O
• Event-based I/O.
• Tornado, Twisted, Gevent (Python).
• EventMachine (Ruby).

38. 1. NON BLOCKING I/O
• Event-based I/O.
• Tornado, Twisted, Gevent (Python).
• EventMachine (Ruby).
• Node.JS (Javascript).

39. 1. NON BLOCKING I/O
• Event-based I/O.
• Tornado, Twisted, Gevent (Python).
• EventMachine (Ruby).
• Node.JS (Javascript).

40. WHY NODE.JS?

41. WHY NODE.JS?

42. WHY NODE.JS?
JAVASCRIPT IS FASTEST
SCRIPTING LANGUAGE

43. WHY NODE.JS?
JAVASCRIPT IS FASTEST
SCRIPTING LANGUAGE
WHEN USING V8

44. WHY NODE.JS?
GOOGLE V8

45. WHY NODE.JS?

46. WHY NODE.JS?
Dynamic Machine Code Generation
point.x

47. WHY NODE.JS?
Dynamic Machine Code Generation
point.x
cmp ebx, [cached_hidden_class]
jne cache_miss
mov eax, ebx

48. WHY NODE.JS?

49. WHY NODE.JS?
ASYNCHRONOUS
NON-BLOCKING BY DEFAULT

50. WHY NODE.JS?
OPEN SOURCE
&
COMMUNITY SUPPORTED

51. WHY NODE.JS?
WEB DEVELOPER FRIENDLY

52. WHY NODE.JS?
HAS PACKAGE MANAGER
$ npm install antigravity

53. WHY NODE.JS?

54. WHY NODE.JS?
LONG POLLING IS HARD

55. WHY NODE.JS?
LONG POLLING IS EASY

56. WHY NODE.JS?

57. WHY NODE.JS?
CODE EXAMPLE:
client.open(function(err, db){
db.query("select * from users", function(err, result){
// do with result
});
});

58. WHY NODE.JS?

59. WHY NODE.JS?
CODE EXAMPLE:
SIMPLE HTTP SERVER
var net = require('net');
var server = net.createServer(function (stream) {
stream.write('hellorn');
stream.on('data', function (data) {
stream.write(data);
});
stream.on('end', function () {
stream.end('goodbyern');
});
});
server.listen(80, 'localhost');

60. WHY NODE.JS?

61. WHY NODE.JS?
CREATE PUB/SUB SERVER
JUST IN 3 LINE OF CODE!
SERIOUS!?

62. WHY NODE.JS?
CREATE PUB/SUB SERVER
JUST IN 3 LINE OF CODE!
SERIOUS!?
var Faye = require('faye'),
server = new Faye.NodeAdapter({mount: '/'});
server.listen(8000);

63. 2. NOSQL DB

64. 2. NOSQL DB

65. 2. NOSQL DB
WHY REDIS?

66. 2. NOSQL DB
WHY REDIS?
Async
SEMI PERSISTENT

67. 2. NOSQL DB
WHY REDIS?
DECR, DECRBY, DEL, EXISTS, GET, GETSET, HDEL,
HEXISTS, HGET, HGETALL, HINCRBY, HKEYS, HLEN,
HMSET, HSET, HVALS, INCR, INCRBY, KEYS, LINDEX, LLEN,
LPOP, LPUSH, LRANGE, LREM, LSET, LTRIM, MGET, MSET,
RICHER THAN MEMCACHED
MSETNX, RENAME, RENAMENX, RPOP, RPOPLPUSH,
RPUSH, SADD, SCARD, SDIFF, SDIFFSTORE, SET, SETNX,
SINTER, SINTERSTORE, SISMEMBER, SMEMBERS, SMOVE,
SORT, SPOP, SRANDMEMBER, SREM, SUNION,
SUNIONSTORE, TTL, TYPE, ZADD, ZCARD, ZINCRBY,
ZRANGE, ZRANGEBYSCORE, ZREM,
ZREMRANGEBYSCORE, ZREVRANGE, ZSCORE

68. 2. NOSQL DB

69. 2. NOSQL DB
WHO’S USING REDIS?

70. 2. NOSQL DB
WHO’S USING REDIS?

71. 2. NOSQL DB

72. 2. NOSQL DB
NODE.JS + REDIS:
$ npm install redis

73. 2. NOSQL DB

74. 2. NOSQL DB
CODE EXAMPLE:
var redis = require("redis"),
client = redis.createClient();
client.set("user.id:1", "robin", redis.print);
client.get("user.id:1",
function(err, replies){
console.log(replies);
client.quit();
});

75. 3. THROTTLING

76. 3. THROTTLING
• Prevent flooding attack.

77. 3. THROTTLING
• Prevent flooding attack.
• Limit input/request per minute/hour/day.

78. 3. THROTTLING
• Prevent flooding attack.
• Limit input/request per minute/hour/day.
• goog.async.Throttle() -- Google Closure Library.

79. Thanks!
r@nosql.asia