redshift_Amazon Redshift架构

redshift

数据仓库| 亚马逊Redshift (Data Warehousing | Amazon Redshift)

Data Engineers or even analysts, it is important to understand the technology to utilise it fully and efficiently. In many cases, Redshift is seen as a traditional database like SQL Server and management is left to DBAs. I would argue that if Redshift best practices are followed, the role of dedicated DBA diminishes to occasional management and upkeep.

数据工程师乃至分析师，了解该技术以充分，有效地利用它很重要。 在许多情况下，Redshift被视为像SQL Server这样的传统数据库，而管理则留给DBA。 我会争辩说，如果遵循Redshift最佳实践，则专用DBA的角色将减少偶发性管理和维护。

In this post, we’ll discover the architecture and understand the effect and impact each component has on queries.

在本文中，我们将探索架构，并了解每个组件对查询的影响和影响。

单纯的观点 (Simplistic View)

From 10,000 ft, Redshift appears like any other relational database with fairly standard SQL and entities like tables, views, stored procedures, and usual data types.

在10,000英尺的高度上，Redshift看起来像任何其他具有相当标准SQL的关系数据库以及诸如表，视图，存储过程和常用数据类型之类的实体。

We’ll start with Tables as these are containers for persistent data storage and will allow us to dive vertically into the architecture. This is what Redshift looks like from 10,000 ft:

我们将从表开始，因为表是用于持久数据存储的容器，并且将使我们能够垂直进入体系结构。 这是10,000英尺的Redshift的样子：

Simplistic 10,000ft view

10,000英尺的简单视图

Redshift is a clus