Scio

A Scala API for Apache Beam and Google Cloud Dataflow. (by spotify)

Scio Alternatives

Similar projects and alternatives to Scio

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Scio alternative or higher similarity.

Scio reviews and mentions

Posts with mentions or reviews of Scio. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-14.
  • what popular companies uses Scala?
    3 projects | reddit.com/r/scala | 14 May 2022
    Apache Beam API called Scio. They open sourced it https://spotify.github.io/scio/
  • Wanting to move away from SQL
    2 projects | reddit.com/r/dataengineering | 25 Feb 2022
    I agree 100%. I haven't used SQL that much in previous data engineering roles, and I refuse to consider jobs that mostly deal with SQL. One of my roles involved using a nice Scala API for apache beam called Scio and it was great. Code was easy to write, maintain, and test. It also worked well with other services like PubSub and BigTable.
  • ETL Pipelines with Airflow: The Good, the Bad and the Ugly
    7 projects | news.ycombinator.com | 8 Oct 2021
    If you prefer Scala, then you can try Scio: https://github.com/spotify/scio.
  • ELT, Data Pipeline
    4 projects | dev.to | 1 Jan 2021
    To counter the above mentioned problem, we decided to move our data to a Pub/Sub based stream model, where we would continue to push data as it arrives. As fluentd is the primary tool being used in all our servers to gather data, rather than replacing it we leveraged its plugin architecture to use a plugin to stream data into a sink of our choosing. Initially our inclination was towards Google PubSub and Google Dataflow as our Data Scientists/Engineers use Big Query extensively and keeping the data in the same Cloud made sense. The inspiration of using these tools came from Spotify’s Event Delivery – The Road to the Cloud. We did the setup on one of our staging server with Google PubSub and Dataflow. Both didn't really work out for us as PubSub model requires a Subscriber to be available for the Topic a Publisher streams messages to, otherwise the messages are not stored. On top of it there was no way to see which messages are arriving. During this the weirdest thing that we encountered was that the Topic would be orphaned losing the subscribers when working with Dataflow. PubSub we might have managed to live with, the wall in our path was Dataflow. We started off with using SCIO from Spotify to work with Dataflow, there is a considerate lack of documentation over it and found the community to be very reserved on Github, something quite evident in the world of Scala for which they came up with a Code of Conduct for its user base to follow. Something that was required from Dataflow for us was to support batch write option to GCS, after trying our hand at Dataflow to no success to achieve that, Google's staff at StackOverflow were quite responsive and their response confirmed that it was something not available with Dataflow and streaming data to BigQuery, Datastore or Bigtable as a datastore was an option to use. The reason we didn't do that was to avoid high streaming cost to these services to store data, as majority of our jobs from the data team are based on batched hourly data. The initial proposal to the updated pipeline is shown below.
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 7 Dec 2022
    InfluxDB is the Time Series Data Platform where developers build real-time applications for analytics, IoT and cloud-native services in less time with less code. Learn more →

Stats

Basic Scio repo stats
6
2,401
9.4
4 days ago
Workflow assistant built for devs & their teams
Automate the mundane part of your day, with live actionable messages for your GitHub & Jira tasks.
www.zigi.ai