MongoDB, RabbitMQ y Applicaciones en Nube
0 likes619 views
This document discusses RabbitMQ, MongoDB, and cloud applications. RabbitMQ is an open source message broker based on AMQP. It supports pub/sub and queuing. MongoDB is a schemaless document database for storing complex hierarchical data and simple analytics. It is not suited for transactions or OLAP. The document provides examples of common operations like select statements, upserts, and indexing in MongoDB. It also lists pros, cons, and tips for using MongoDB and references additional resources.
More Related Content
![[POSS 2019] OVirt and Ceph: Perfect Combination.?](https://cdn.slidesharecdn.com/ss_thumbnails/pre-poss2019-worteks-ovirt-ceph-191216145947-thumbnail.jpg?width=560&fit=bounds)
Similar to MongoDB, RabbitMQ y Applicaciones en Nube (20)
MongoDB, RabbitMQ y Applicaciones en Nube
- 1. MongoDB, RabbitMQ y aplicaciones en nube Gustavo Arjones [email protected] | @arjones
- 2. Arquitectura orientada a msjs
- 5. RabbitMQ • Message Queue (AMQP compliance) • Arquitectura orientada a mensajes • Desacoplado, Aislado • Facil escalabilidad horizontal • “AlternaAva”: Kestrel / Twi8er (NO AMQP!)
- 7. Direct Message Matching exact key Cerveza Cerveza Cerveza Vino
- 8. Fanout Exchange Copy to all Cerveza Cerveza Cerveza Bebida Bebida
- 9. Topic Exchange Route by Key with Key Globbing Bebida.Vino Bebida.Vino Bebida.Vino Bebida.# Comida.* #.Vino
- 10. Nanite • Nanite is a new way of thinking about building cloud ready web applicaAons. Having a scalable message queueing back-‐end with all the discovery and dynamic load based dispatch that Nanite has is a very scalable way to construct web applicaAon back-‐ends.
- 12. MongoDB es … • DB Orientado a documentos (schemaless) • “Facil” escalar horizontal (shard) • Para mantener estructuras complejas (jerarquicas) • Para estadísAcas “simples” • Para mantener archivos (GridFS)
- 13. MongoDB NO es … • Para transaciones • Para OLAP • RDBMS (AcAveRecord?)
- 14. Select SELECT first_name, last_name FROM authors WHERE zipcode = 1234 ORDER BY last_name DESC LIMIT 2, 1; > db.authors.find({"zipcode" : 1234}, {"first_name" : 1, "last_name" : 1 }).sort({"last_name" : -‐1 }) .skip(2).limit(1);
- 15. Select SELECT * FROM authors WHERE dob BETWEEN ‘1970-‐1-‐1’ AND ‘1990-‐1-‐1’ AND address IS NULL; > db.authors.find({"dbo" : { $gte : new Date(“1970-‐1-‐1”), $lte : new Date(“1990-‐1-‐1”)}, “address” : { $exists : false } } );
- 16. Upsert (Update + Insert) > db.tweets.update( query, modify, upsert?, mul2ple? ); > db.setup.update({}, { $set : { "in_progress" : false } }, false, true); > db.setup.update({}, { "opAons.last_status" : -‐1}, false, true);
- 17. Indexes > db. tweets.ensureIndex( {"user.Ame_zone" : 1}, {background:true}); > db.tweets.ensureIndex( {"created_at" : 1, "user.Ame_zone" : 1, "tokens" : 1}, {background:true}); background:true no lock para crear indices > db.tweets.getIndexes()
- 18. Prós Contras • Schemaless • Map-‐Reduce MUY lento • Rápida instalación • Sharding es BETA • Muchos Drivers • Nuevo set de disponibles commandos
- 19. Tips • Pensar BIEN el schema antes de empezar • Guardar calculaAon • Evitar map-‐reduce (unAl r. 1.8) • Indexes TIENEN que entrar en RAM > db. tweets.totalIndexSize(); 1187423168 (~1.1Gb) > db. tweets.storageSize(); 16670199040 (~15.5 Gb)
- 20. Referencias • h8p://www.rabbitmq.com/ • h8p://www.mongodb.org/ • h8p://github.com/ezmobius/nanite • h8p://github.com/robey/kestrel • h8p://www.slideshare.net/somic/introducAon-‐ to-‐amqp-‐messaging-‐with-‐rabbitmq • h8p://www.slideshare.net/ma8ma8/rabbitmq-‐ and-‐nanite
- 21. Muchas gracias Gustavo Arjones [email protected] | @arjones