Microservices using Node.js and RabbitMQ

I would like to share a real case project I have worked on for a startup, in Sao Francisco. The ideia is to explore how we dealt with this architecture, what we have learned so far and how it is to start doing microservices from scratch.
Did this architecture benefit us? What were the good and bad parts?
Using a simple API I am going to explain the basics about microservices and when/how RabbitMQ comes in handy.

Transcript

1. MICROSERVICES USING NODE.JS AND RABBITMQ
3. Case Microservices RabbitMQ Conclusion
4. Case
5. Share your location with your friends
7. API Back-end
8. Key = DevOps
9. Microservices ↓ Microdeployments
10. Reasons
11. Team
12. Architecture
13. Best Practices
14. Code Review
15. Tests
16. Continuous Integration
17. Continuous Delivery
18. Continuous Monitoring
19. User Message Lorem Ipsum Dolor Sit Amet
20. Libraries
21. Results after 10 months
22. Startup 5 back-end developers 7 micro-services
23. Positives
24. New technologies
25. Minimum effort/impact
26. MySQL MySQL Postgre SQL Postgre SQL MySQL Postgre SQL Postgre SQL
27. Polyglot Persistence
28. Decoupled Code
29. Each service has a scope
30. Negatives
31. Shotgun effect
33. Granular Release
34. Unstable Interfaces
35. User Message
36. Integration Tests
37. Slow
38. Docker
39. New developers
40. User-service dependency
41. User Message Lorem Ipsum Dolor Sit Amet
42. Lorem Ipsum Dolor Amet
43. Microservices
45. Client Server
46. Server
47. 1 const express = require('express'); 2 const bodyParser = require('body-parser'); 3 4 const app = express(); 5 app.use(bodyParser.json()); 6 7 app.listen(3000, () => { 8 console.log(' [x] Awaiting for requests'); 9 }); 10 11 app.get('/:id', (request, response) => { 12 const id = request.params.id; 13 14 console.log(` [.] ID ${id}`); 15 16 response.status(200).json({ 17 data: { 18 name: 'Ada Lovelace', 19 occupation: 'Programmer' 20 } 21 }); 22 });
48. 1 app.listen(3000, () => { 2 console.log(' [x] Awaiting for requests'); 3 }); 4 5 app.get('/:id', (request, response) => { 6 const id = request.params.id; 7 8 console.log(` [.] ID ${id}`); 9 10 response.status(200).json({ 11 data: { 12 name: 'Ada Lovelace', 13 occupation: 'Programmer' 14 } 15 }); 16 });
49. Client
50. 1 const express = require('express'); 2 const request = require('request-promise'); 3 4 const id = process.argv.slice(2); 5 6 const app = express(); 7 8 app.listen(3005, () => { 9 console.log(` [x] Requesting user ${id}`); 10 11 request(`http://localhost:3000/${id}`) 12 .then((res) => { 13 return console.log(` [.] Got ${res}`) 14 }); 15 });
51. 1 const id = process.argv.slice(2); 2 3 app.listen(3005, () => { 4 console.log(` [x] Requesting user ${id}`); 5 6 request(`http://localhost:3000/${id}`) 7 .then((res) => { 8 return console.log(` [.] Got ${res}`) 9 }); 10 });
52. Result
54. Client
55. Fault resilience
56. Message Broker
58. AMPQ Advanced Message Queuing Protocol
59. Exchange asynchronous messages
60. Reliability
61. RPC Remote Procedure Call
63. Queueing
64. Client Server RPC
65. Server
66. 1 const amqp = require('amqplib/callback_api'); 2 3 amqp.connect('amqp://localhost', (err, conn) => { 4 conn.createChannel((err, ch) => { 5 const q = 'rpc_queue'; 6 7 ch.assertQueue(q, { durable: false }); 8 ch.prefetch(1); 9 10 console.log(' [x] Awaiting RPC requests'); 11 12 ch.consume(q, function reply(msg) { 13 const id = parseInt(msg.content.toString(), 10); 14 15 console.log(` [.] ID ${id}`); 16 17 ch.sendToQueue(msg.properties.replyTo, 18 new Buffer('name: Ada Lovelace, occupation: programmer'), 19 { correlationId: msg.properties.correlationId }); 20 21 ch.ack(msg); 22 }); 23 }); 24 });
67. rpc_queue Response Channel 3 amqp.connect('amqp://localhost', (err, conn) => { 4 conn.createChannel((err, ch) => { 5 const q = 'rpc_queue';
68. Retrieve message from rpc_queue 12 ch.consume(q, function reply(msg) { 13 const id = parseInt(msg.content.toString(), 10); 14 15 console.log(` [.] ID ${id}`);
69. Send response to callback queue 17 ch.sendToQueue(msg.properties.replyTo, 18 new Buffer('name: Ada Lovelace, occupation: programmer’), 19 { correlationId: msg.properties.correlationId });
70. Client
71. 1 const amqp = require('amqplib/callback_api'); 2 const uuid = require('uuid'); 3 4 const id = process.argv.slice(2); 5 6 amqp.connect('amqp://localhost', (err, conn) => { 7 conn.createChannel((err, ch) => { 8 ch.assertQueue('', { exclusive: true }, (err, q) => { 9 10 const corr = uuid(); 11 console.log(` [x] Requesting user ${id}`); 12 13 ch.consume(q.queue, (msg) => { 14 if (msg.properties.correlationId === corr) { 15 console.log(` [.] Got ${msg.content.toString()}`); 16 setTimeout(function() { conn.close(); process.exit(0) }, 500); 17 } 18 }, {noAck: true}); 19 20 ch.sendToQueue('rpc_queue', 21 new Buffer(id.toString()), 22 { correlationId: corr, replyTo: q.queue }); 23 }); 24 }); 25 });
72. Callback Queue Request Channel 6 amqp.connect('amqp://localhost', (err, conn) => { 7 conn.createChannel((err, ch) => { 8 ch.assertQueue('', { exclusive: true }, (err, q) => {
73. Request to rpc_queue 10 const corr = uuid(); 20 ch.sendToQueue('rpc_queue', 21 new Buffer(id.toString()), 22 { correlationId: corr, replyTo: q.queue });
74. Retrieve response from callback queue 13 ch.consume(q.queue, (msg) => { 14 if (msg.properties.correlationId === corr) { 15 console.log(` [.] Got ${msg.content.toString()}`); 16 setTimeout(function() { conn.close(); process.exit(0) }, 500); 17 } 18 }, {noAck: true});
75. Result
77. Scalability
78. Round-Robin
79. Queues Performance
80. Conclusion
82. Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. Conway's Law
83. Engineering
84. Trade-Off
85. How to solve my team problems?
86. Shotgun effect Unstable interfaces Integration tests User-service dependency
87. Monolith
88. Partially
89. User Message Lorem Ipsum Dolor Sit Amet
90. User Lorem Ipsum
91. Shotgun effect Unstable interfaces Integration tests User-service dependency
92. Community
98. Let technology empower you!
99. Thanks!
100. https://github.com/carolpc https://twitter.com/CarolinaPascale carolina.pascale.c@gmail.com