NoSQL 架构白皮书

发布于 2025-01-05 15:22:27 字数 269 浏览 2 评论 0原文

我想更好地了解 RabbitMQ、MongoDb、Node.Js 和 Hadoop 等技术如何整合到系统架构中以提供高可用性/可扩展性/性能。

谁能指导我找到此类信息的良好来源?

编辑

诚然,这不是一个好问题,我应该澄清一下。我并不是在寻找上述堆栈中任何技术的细节,我了解它们每个人的作用以及如何使用它们的一些知识。我正在寻找的是一个利用消息队列/NoSQL/Map reduce/事件驱动语言的系统规范,这样我就可以更好地理解它们如何协同工作以提供高可用性/可扩展性/性能。

I want to better understand how technologies like RabbitMQ, MongoDb, Node.Js and Hadoop fit together into a system architecture to provide high-availability/scalability/performance.

Can anyone direct me to a good source for this sort of information?

EDIT

Admittedly, this isn't a great question, I should clarify. I'm not looking for specifics on any of the techs in the above stack, I have an understanding of what each of them do and some knowledge of how to use them. What I'm looking for is a specification for a system that leverage's message queue/NoSQL/Map reduce/event driven lang so I can better understand how they work together to deliver high-availability/scalability/performance.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

樱花落人离去 2025-01-12 15:22:27

如果我是你,我会先关注整体系统设计,然后再关注特定技术。 RabbitMQ 将消息从一个地方传输到另一个地方,MongoDB 存储文档,Node.JS 处理 HTTP 请求,Hadoop 存储和存储数据。处理数据。每个系统都有不同的竞争对手。

我会查看来自 highscalability.com 博客的现实生活架构。我还会查看 CAP 论文,其中列出了“可用的”内容“ 方法。

If I were you I would focus on the overall system design before focusing on specific technologies. RabbitMQ transports messages from place to place, MongoDB stores documents, Node.JS processes HTTP requests, and Hadoop stores & process data. Each of those systems has various competitors.

I'd check out real life architectures from the highscalability.com blog. I would also check out the CAP paper that lays out what exactly "available" means.

囍孤女 2025-01-12 15:22:27

似乎您正在要求在“为什么我应该使用它而不是 LAMP/Ruby/Python/$YourOldStackHere”的上下文中对 NodeJS 进行一般介绍,

我唯一可以建议的是:观看一堆 nodeJS 视频,阅读 http://nodebeginner.org,并开发一个简单的应用程序来感受这一切。

至于它们如何“整合到一个系统架构中以提供高可用性/可扩展性/性能”,嗯,它们符合您的期望; Node 提供了一种快速的事件驱动语言,memcache/redis/mongo 提供了一个(非)持久键/值存储,它放弃了许多 SQL 驱动解决方案实际上不需要的 SQL 的关系方面,并将其交换为速度。

“高可用性/可扩展性/性能”都归结为技术在硬件上的运行速度。快速的事物更具可扩展性、可用性和性能。 NodeJS 构建于 V8 之上,V8 是最快的 JS 引擎,但如果您与 PHP 等进行比较,这并没有任何意义。

快速谷歌肯定会提供一些“node vs $YourStack”的分析

Seems like you're asking for a general intro to NodeJS in the context of "Why should I use this instead of LAMP/Ruby/Python/$YourOldStackHere"

The only thing I can suggest is: watch a bunch of nodeJS videos, read http://nodebeginner.org, and develop a simple application to get a feel for it all.

As far as how they "fit together into a system architecture to provide high-availability/scalability/performance", well, they fit as you'd expect them to; Node provides a fast event-driven language, memcache/redis/mongo provides a (non)persistent key/value store which drops the relational aspect of SQL which many SQL-driven solutions don't actually need, and swaps it for speed.

"high-availability/scalability/performance" all boil down to how fast the tech is on your hardware. Fast things are more scalable, available, performant. NodeJS is built on V8 which is the fastest JS engine, but that doesn't really mean anything if you're comparing to eg PHP.

A quick google will surely provide some analyses of "node vs $YourStack"

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文