wjones127 commented on code in PR #348:
URL: https://github.com/apache/arrow-site/pull/348#discussion_r1181266067
##########
_posts/2023-04-24-adopting-apache-arrow-at-cloudquery.md:
##########
@@ -0,0 +1,65 @@
+---
+layout: post
+title: "Adopting Apache Arrow at CloudQuery"
+date: "2023-04-30 00:00:00"
+author: Yevgeny Pats
+categories: [application]
+---
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+
+This post is a collaboration with CloudQuery and cross-posted on the
CloudQuery
[blog](https://cloudquery.io/blog/adopting-apache-arrow-at-cloudquery).
+
+[CloudQuery](https://github.com/cloudquery/cloudquery) is an open source high
performance ELT framework written in Go. We
[previously](https://www.cloudquery.io/blog/building-cloudquery) discussed some
of the [architecture](https://www.cloudquery.io/docs/developers/architecture)
and design decisions that we took to build a performant ELT framework. A type
system is a key component for creating a performant and scalable ELT framework
where sources and destinations are decoupled. In this blog post we will go
through why we decided to adopt Apache Arrow as our type system and replace our
in-house implementation.
+
+# What is a Type System?
+
+Let’s quickly
[recap](https://www.cloudquery.io/blog/building-cloudquery#type-system) what a
type system is and why an ELT framework needs one. At a very high level, an ELT
framework extracts data from some source and moves it to some destination with
a specific schema.
+
+```text
+API ---> [Source Plugin] -----> [Destination Plugin]
+ -----> [Destination Plugin]
+ gRPC
+```
+
+
+Sources and destinations are decoupled and communicate via gRPC. This is
crucial to allowing the addition of new destinations and updating old
destinations without requiring updates to source plugin code (which otherwise
would introduce an unmaintainable architecture).
+
+This is where a type system comes in. Source plugins extract information from
APIs in the most performant way possible, defining a schema and then
transforming the result from the API (JSON or any other format) to a
well-defined type system. The destination plugin can then easily create the
schema for its database and transform the incoming data to the destination
types. So to recap, the source plugin sends mainly two things to a destination:
1) Schema 2) Data that fits the defined schema (Arrow Arrays).
Review Comment:
```suggestion
This is where a type system comes in. Source plugins extract information
from APIs in the most performant way possible, defining a schema and then
transforming the result from the API (JSON or any other format) to a
well-defined type system. The destination plugin can then easily create the
schema for its database and transform the incoming data to the destination
types. So to recap, the source plugin sends mainly two things to a destination:
1) the schema 2) the records that fit the defined schema. In Arrow terminology,
these are a schema and a record batch.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
