Stream-Framework VS sgr

Compare Stream-Framework vs sgr and see what are their differences.

Stream-Framework

Stream Framework is a Python library, which allows you to build news feed, activity streams and notification systems using Cassandra and/or Redis. The authors of Stream-Framework also provide a cloud service for feed technology: (by tschellenbach)

sgr

sgr (command line client for Splitgraph) and the splitgraph Python library (by splitgraph)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Stream-Framework sgr
34 22
4,713 324
- 0.3%
0.0 5.4
10 months ago 6 months ago
Python Python
GNU General Public License v3.0 or later GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Stream-Framework

Posts with mentions or reviews of Stream-Framework. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-29.
  • On what side project you guys are working on?
    14 projects | /r/webdev | 29 Jun 2023
    An ultralight social media app with no dependencies that can run on shared web hosting. It's an API like Getstream, so F/E is up to you. I've had a fork of it in production for 2.5 years on a subscription site that generates a small income.
  • I need advice and help.
    2 projects | /r/swift | 16 May 2023
    Think about the edge that you can have over thousands other people looking for a job like you. One of the ways to do it – tailor your (even small) experience to the company you are applying to. E.g. Let's take a company like Stream that have an open-source Swift SDK, try to contribute to their SDK, maybe close some `good-first-issue`s here and there, do some documentation improvements, enrich their example app. So that when you feel like you are ready to knock their door – you already have an edge over others – you don't need onboarding (because you already know most of their codebase, you even completed your first few tasks while yet not being employed!)
  • We need to talk about how Reddit handles automated permabans of mods
    2 projects | /r/ModSupport | 28 Apr 2023
    I firmly believe the tier 1 admins are just this program - https://getstream.io/
    2 projects | /r/ModSupport | 28 Apr 2023
    I too firmly believe the tier 1 admins are just this program - https://getstream.io/ And reddit doesn't want to admit that humans are not actually reviewing things
  • Building a functional Twitter clone in a weekend
    3 projects | /r/programming | 11 Apr 2023
  • Building a Site for a community based on shared interests?
    2 projects | /r/web_design | 3 Apr 2023
    Really depends on so many variables, and comes down to knowing the audience. I built a lightweight social network api platform to do a lot of what getstream.io and OSSN does, but the way users engaged with it was nothing like what I expected. One use case, for example, would have been mostly satisfied with WordPress and Mailchimp. Forums are very familiar to people and still used by a lot of "I don't do social media" types. At the risk of making a sweeping generalization, if you have an older target audience they will be happy with a forum. If you have a younger target audience they will prefer the sequential post / react style of interacting, like Discord or Instagram.
  • Adding live chat support for Flutter Web
    3 projects | /r/FlutterDev | 28 Feb 2023
  • React Native Stack Suggestions
    3 projects | /r/reactnative | 7 Feb 2023
  • Create a customer-admin chat portal for online ordering website
    2 projects | /r/react | 30 Jan 2023
    Have you worked with Stream before? I think it's what you're looking for.
  • Ask HN: Best and Worst API Documentations?
    4 projects | news.ycombinator.com | 8 Sep 2022
    I really like https://getstream.io/ docs. For me, SDK support is important, as are examples and templates that I can play with & build off of. I also like the API usage dashboard that Stream supplies when you login. Which veers into the terriory of dev portal, but worth mentioning.

    Also, in terms of tools for actually building documentation, I recommend looking at https://docusaurus.io/ for clean, customisable documentation.

sgr

Posts with mentions or reviews of sgr. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-01.
  • Release engineering is exhausting so here's cargo-dist
    12 projects | news.ycombinator.com | 1 Feb 2023
    I wrote up the details of this in a PR [0] where I last dealt with it.

    [0] https://github.com/splitgraph/sgr/pull/656

  • Ask HN: Serverless SQLite or Closest DX to Cloudflare D1?
    2 projects | news.ycombinator.com | 2 Jan 2023
    This is the vision of what we're building at Splitgraph. [0] You might be most interested in our recent project Seafowl [1] which is an open-source analytical database optimized for running "at the edge," with cache-friendly semantics making it ideal for querying from Web applications. It's built in Rust using DataFusion and incorporates many of the lessons we've learned building the Data Delivery Network [2] for Splitgraph.

    [0] https://www.splitgraph.com

    [1] https://seafowl.io

    [2] https://www.splitgraph.com/connect

  • Postgres Auditing in 150 lines of SQL
    10 projects | news.ycombinator.com | 9 Mar 2022
    You might like what we're doing with Splitgraph. Our command line tool (sgr) installs an audit log into Postgres to track changes [0]. Then `sgr commit` can write these changes to delta-compressed objects [1], where each object is a columnar fragment of data, addressable by the LTHash of rows added/deleted by the fragment, and attached to metadata describing its index [2].

    I haven't explored sirix before, but at first glance it looks like we have some similar ideas — thanks for sharing, I'm excited to learn more, especially about its application of ZFS.

    [0] https://www.splitgraph.com/docs/working-with-data/tracking-c...

    [1] https://www.splitgraph.com/docs/concepts/objects

    [2] https://github.com/splitgraph/splitgraph/blob/master/splitgr...

  • The world of PostgreSQL wire compatibility
    3 projects | news.ycombinator.com | 10 Feb 2022
    Shameless plug, but your list is missing Splitgraph [0] :)

    We’ve been based on Postgres from the beginning, and although the backend is a bit more complex at this point, we’ve kept the wire protocol intact. We’re also heavily invested in FDWs, not only for federated queries (e.g. querying data at Snowflake – btw, you might enjoy our blog post on achieving a 100x speedup with aggregation pushdown), but also for queries on warehoused data stored as Splitgraph images. By keeping Postgres compatibility as our guiding constraint, we’ve been able to build a lot of functionality on top of just a few simple abstractions. The result is something akin to a magic Postgres database – you can connect dozens of live sources to it using FDW plugins, or you can ingest from hundreds data sources using Airbyte connectors, ultimately storing the data as immutable Splitgraph images in object storage.

    As for the wire protocol, our implementation is heavily reliant on (a forked version of) PgBouncer. Basically, a query arrives, we parse it for references to tables (which look like Docker image tags), and the proxy layer performs whatever orchestration is necessary to satisfy the query. That could mean instantiating a foreign server to a saved connection, loading some data from object storage, or even lazily loading only the requisite data (we call this “layered querying” since it’s implemented similarly to AUFS). In the future, it could also mean delegating the query to a more specialized engine like Presto.

    Point is, by keeping the frontend intact, we’re able to retain compatibility with all Postgres clients, but we’re free to implement the backend in more scalable or domain specific ways. For example, we’re able to horizontally scale our query capacity by simply adding more “cache nodes” that perform the layered querying.

    We are definitely all-in on the Postgres wire protocol, and all the ecosystem compatibility that comes along with it. You can read our blog for more in depth discussions of this, but I don’t want to spam too many links here. :)

    [0] https://www.splitgraph.com

    [1] https://www.splitgraph.com/blog/postgresql-fdw-aggregation-p...

  • Scalable PostgreSQL Connection Pooler
    11 projects | news.ycombinator.com | 12 Nov 2021
    We are building a solution for this problem at Splitgraph [0] – it sounds like we could probably help with your use case. You can get it to work yourself with our open source code [1], but our (private beta, upcoming public) SaaS service will put all your schemas on a more scalable “data delivery network,” which incidentally, happens to be implemented with PgBouncer + rewriting + ephemeral instances. In a local engine (just a Postgres DB managed by Splitgraph client to add extra stuff), there is no PgBouncer, but we use Foreign Data Wrappers to accomplish the same.

    On Splitgraph, every dataset – and every version of every dataset – has an address. Think of it like tagged Docker images. The address either points to an immutable “data image” (in which case we can optionally download objects required to resolve a query on-the-fly, although loading up-front is possible too) or to a live data source (in which case we proxy directly to it via FDW translation). This simple idea of _addressable data products_ goes a long way – for example, it means that computing a diff is now as simple as joining across two tables (one with the previous version, one with the new).

    Please excuse the Frankenstein marketing site – we’re in the midst of redesign / rework of info architecture while we build out our SaaS product.

    Feel free to reach out if you’ve got questions. And if you have a business case, we have spots available in our private pilot. My email is in my profile – mention HN :)

    [0] https://www.splitgraph.com/connect

    [1] examples: https://github.com/splitgraph/splitgraph/tree/master/example...

  • Ask HN: How to get compeitors to use our open source interop-prototcol?
    4 projects | news.ycombinator.com | 4 Oct 2021
    Federated data sharing is the core use case of the magic Postgres database we’re building at Splitgraph [0]. We’d love to help you solve these problems! The ideas you’re describing are exactly what we want to achieve – data sharing should be as easy as changing a connection string in a SQL client. It sounds like your use case would be a good fit for what we’re building. If you’d like to learn more, please send me a note – email in profile.

    [0] https://www.splitgraph.com

  • Cloudera taken private for $5.3b, acquires Datacoral and Cazena
    2 projects | news.ycombinator.com | 1 Jun 2021
    The data industry continues to hype this idea of “multi-cloud,” but then the “modern data stack” is centralized around a single warehouse and nobody sees any irony in that.

    The big bet we’re making at Splitgraph [0] is that the next wave of data engineering will take a more decentralized, “data mesh” type approach to enterprise architecture. “Data gravity” really does exist -expensive to move, in terms of both cost and operational complexity. So instead of bringing the data to the query, why not bring the query to the data? All we need for that is a set of read only credentials.

    Cloudera mentions they bought DataCoral to help with data integration and connectors. They’ve correctly identified the problem - data sprawl and fragmentation will inevitably grow - but I’m not sure they have the right solution.

    Data integration is important, but it’s a moving target, which is why it calls for a collaborative open source solution. This is why so many new startups, like AirByte most recently, are coalescing around the Singer taps that Stitch left behind after its acquisition by Talend.

    We also support using Singer taps to ingest data into versioned Splitgraph images [1], so we’re excited to see more collaboration on maintenance of taps. For us it’s a useful feature, but it should be just that — a feature. Is there really a need to replicate all of your data before you can even query it? Or would you rather experiment by directly querying its source?

    [0] https://www.splitgraph.com

    [1] unreleased and undocumented atm, but it does work. We’re hiring, especially on the frontend if you want to help build the web UI. See profile.

  • Ask HN: Who is hiring? (April 2021)
    21 projects | news.ycombinator.com | 1 Apr 2021
    Splitgraph (https://www.splitgraph.com) | Remote | Full-time

    Splitgraph is reshaping how organizations interact with data. We provide a unified interface to discover and query data. In practice, this means we're building a data catalog (a web app) and query layer (implemented with the Postgres wire protocol).

    We're a seed-stage, venture-funded startup hiring our initial team. The two co-founders are looking to grow the team by adding multiple engineers across the stack. This is an opportunity to make a big impact on an agile team while working closely with the founders.

    Splitgraph is a remote-first organization. The founders are based in the UK, and the company is incorporated in both USA and UK. Candidates are welcome to apply from any geography. We want to work with the most talented, thoughtful and productive engineers in the world.

    Open positions:

    * Senior Software Engineer - Frontend. Responsible for the web stack, mainly involving Typescript, React, Next.js, Postgraphile, etc.

    * Senior Software Engineer - Backend. Responsible for a variety of core services, using Python, Poetry, Postgres, C, Lua, and a ton of other technologies.

    Learn more & apply: https://www.notion.so/splitgraph/Splitgraph-is-Hiring-25b421...

  • Build your own “data lake” for reporting purposes
    4 projects | news.ycombinator.com | 14 Mar 2021
    It's really cool to see these techniques in the wild. We're doing something very similar to implement our "Data Delivery Network" at Splitgraph [0] [1]. Recently we've started calling Splitgraph a "Data Mesh" [2]. As long as we have a plugin [3] for a data source, users can connect external data sources to Splitgraph and make them addressable alongside all the other data on the platform, including versioned snapshots of data called data images. [4] So you can `SELECT FROM namespace/repo:tag` where `tag` can refer to an immutable version of the data, or e.g. `live` to route to route to a live external data source via FDW. So far we have plugins for Snowflake, CSV in S3 buckets, MongoDB, ElasticSearch, Postgres, and a few others, like Socrata data portals (which we use to index 40k open public datasets).

    Our goal with Splitgraph is to provide a single interface to query and discover data. Our product integrates the discovery layer (a data catalog) with the query layer (a Postgres compatible proxy to data sources, aka a "data mesh" or perhaps "data lake"). This way, we improve both the catalog and the access layer in ways that would be difficult or impossible as separate products. The catalog can index live data without "drift" problems. And since the query layer is a Postgres-compatible proxy, we can apply data governance rules at query time that the user defines in the web catalog (e.g. sharing data, access control, column masking, query whitelisting, rewriting, rate limiting, auditing, firewalling, etc.).

    We like to use GitLab's strategy as an analogy. GitLab may not have the best CI, the best source control, the best Kubernetes deploy orchestration, but by integrating them all together in one platform, they have a multiplicative effect on the platform itself. We think the same logic can apply to the data stack. In our vision of the world, a "data mesh" integrated with a "data catalog" can augment or eventually replace various complicated ETL and warehousing workflows.

    P.S. We're hiring immediately for all-remote Senior Software Engineer positions, frontend and backend [5]

    [0] https://www.splitgraph.com

    [1] We talked about all this in depth on a podcast: https://softwareengineeringdaily.com/2020/11/06/splitgraph-d...

    [2] https://martinfowler.com/articles/data-monolith-to-mesh.html

    [3] https://www.splitgraph.com/blog/foreign-data-wrappers

    [4] https://www.splitgraph.com/docs/concepts/images

    [5] Job posting: https://www.notion.so/splitgraph/Splitgraph-is-Hiring-25b421...

    4 projects | news.ycombinator.com | 14 Mar 2021
    Our goal with Splitgraph is to provide a single interface to query and discover data. Our product integrates the discovery layer (a data catalog) with the query layer (a Postgres compatible proxy to data sources, aka a "data mesh" or perhaps "data lake"). This way, we improve both the catalog and the access layer in ways that would be difficult or impossible as separate products. The catalog can index live data without "drift" problems. And since the query layer is a Postgres-compatible proxy, we can apply data governance rules at query time that the user defines in the web catalog (e.g. sharing data, access control, column masking, query whitelisting, rewriting, rate limiting, auditing, firewalling, etc.).

    We like to use GitLab's strategy as an analogy. GitLab may not have the best CI, the best source control, the best Kubernetes deploy orchestration, but by integrating them all together in one platform, they have a multiplicative effect on the platform itself. We think the same logic can apply to the data stack. In our vision of the world, a "data mesh" integrated with a "data catalog" can augment or eventually replace various complicated ETL and warehousing workflows.

    P.S. We're hiring immediately for all-remote Senior Software Engineer positions, frontend and backend [5]

    [0] https://www.splitgraph.com

    [1] We talked about all this in depth on a podcast: https://softwareengineeringdaily.com/2020/11/06/splitgraph-d...

    [2] https://martinfowler.com/articles/data-monolith-to-mesh.html

    [3] https://www.splitgraph.com/blog/foreign-data-wrappers

    [4] https://www.splitgraph.com/docs/concepts/images

    [5] Job posting: https://www.notion.so/splitgraph/Splitgraph-is-Hiring-25b421...

What are some alternatives?

When comparing Stream-Framework and sgr you can also consider the following projects:

django-activity-stream - Generate generic activity streams from the actions on your site. Users can follow any actors' activities for personalized streams.

haystack - :mag: LLM orchestration framework to build customizable, production-ready LLM applications. Connect components (models, vector DBs, file converters) to pipelines or agents that can interact with your data. With advanced retrieval methods, it's best suited for building RAG, question answering, semantic search or conversational agent chatbots.

Baserow - Open source no-code database and Airtable alternative. Create your own online database without technical experience. Performant with high volumes of data, can be self hosted and supports plugins

parabol - Free online agile retrospective meeting tool

dremio-oss - Dremio - the missing link in modern data

django-pgviews - Fork of django-postgres that focuses on maintaining and improving support for Postgres SQL Views.

pgbouncer-fast-switchover - Adds query routing and rewriting extensions to pgbouncer

informant - An Arch Linux News reader and pacman hook

BlingFire - A lightning fast Finite State machine and REgular expression manipulation library.

Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..

fargate-game-servers - This repository contains an example solution on how to scale a fleet of game servers on AWS Fargate on Elastic Container Service and route players to game sessions using a Serverless backend. Game Server data is stored in ElastiCache Redis. All resources are deployed with Infrastructure as Code using CloudFormation, Serverless Application Model, Docker and bash/powershell scripts. By leveraging AWS Fargate for your game servers you don't need to manage the underlying virtual machines.

web - Grow Open Source