boltstream
Marten
boltstream | Marten | |
---|---|---|
2 | 23 | |
1,737 | 2,670 | |
- | 0.8% | |
1.8 | 9.8 | |
almost 3 years ago | 7 days ago | |
Python | C# | |
Apache License 2.0 | MIT License |
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.
boltstream
-
Amazon's Twitch to Cut 500 Employees, About 35% of Staff
Several years ago I cobbled together all the pieces to make a live video streaming website [1] like Twitch.tv, et al. It's impossible to actually run at any kind of scale without being an ISP or Google-scale peer. Not to mention the enormous amount of DMCAs when people are trying to stream live sports, Pay-per-view, etc.
It was fun to play with it for a couple months. But there's no business here. Twitch.tv is also finding that out.
[1] https://github.com/benwilber/boltstream
-
Ask HN: Show your failed projects and share a lesson you learned
I built Boltstream [0] over the course of a couple years and got burned out. I wouldn't say it was actually a failed project because in the back of my mind I never really had any intention of trying to turn it into a Twitch/YouTube/Facebook Live competitor anyway. And it's proven to be somewhat popular on Github. The project was fun to build and learn about but ultimately it was impossible to actually run it as a consumer-facing website. The problems were never the actual software/video streaming tech, but rather the extreme bandwidth costs of live video streaming, and the content itself. I launched it several times under different site names/products and it always just turned into a cesspool of pirate streaming live sports and other copyrighted content. The DMCA notices were regular, but were never really that onerous to deal with. Just turn the stream off, ban the account, and then reply to the email. But it just got too annoying. I built a little mobile web app so I could just do it from my phone while I was out at dinner. After awhile I just decided that it was time to give it to someone else to play with. So I did a big code dump on Github and haven't touched it since.
I've actually started working on it a little bit more recently since it seems that "self hosted video streaming" is still pretty in-demand. I'm probably not going to be spending too much time on the actual features and functionality since that's pretty much done at this point. Mostly just packaging it up so it's easier for people to run it themselves and hack on it.
[0] https://github.com/benwilber/boltstream
Marten
- Marten – .NET Transactional Document DB and Event Store on PostgreSQL
-
Dapper vs. Entity Framework With Postgres
Id recommend trying out MartenDb. It's not really a PostgreSQL ORM, it actually uses Postgres more as a document database via jsonb. But it's excruciatingly easy to use and schema updates are a breeze (and largely automatic)
-
Show HN: Light implementation of Event Sourcing using PostgreSQL as event store
Check out Marten for a fully fleshed out implementation https://github.com/JasperFx/marten
-
Is anyone using Dapr
We are using ExtCore here to make our app modular: https://extcore.net/, and MartenDB for event store (which is surprisingly VERY simple) : https://martendb.io/
-
Yet another embedded DB (kind of)
I always loved Marten, it is so simple to use and yet powerful. If you are unfamiliar with it, it is a data access library (like an ORM) that is using JSON serialization and LINQ to store and query data from/to Postgres. It basically turns Postgres into document DB. Comparing it to EF, Marten doesn't require migrations since it stores documents.
-
This article is covering the potential problems you will face when using MongoDB for typical relational tasks.
You're better off using Postgres (has JSON columns.) If you want a more "document" oriented experience, use Marten: https://martendb.io/
-
Self-Paced Kit: Introduction to Event Sourcing with Node.js and TypeScript
For that part, the samples use EventStoreDB (https://www.eventstore.com/), which is the only mature event store I know in Node.js land. Event Sourcing allows using any database as backing storage. I'm co-maintainer of the Marten (https://martendb.io/), which is a .NET library that allows using Postgres as event store and document db.
-
CQRS is simpler than you think with C#11 and .NET 7!
Then you should check out Marten (https://martendb.io/). Our intention is to remove the boilerplate, we're using Postgres e having the built-in projections.
- Event-driven projections in Marten explained
-
Marten, a Crystal web framework that makes building web apps productive and fun
Not to be confused with the C# document database built on Postgres.
https://martendb.io/
What are some alternatives?
rtti
Event Store - EventStoreDB, the event-native database. Designed for Event Sourcing, Event-Driven, and Microservices architectures
pqm - Physical Quantities and Measures (PQM) is a Node and browser package for dealing with numbers with units
MongoDB - The MongoDB Database
Flythrough.Space - Top down space captain RPG
RavenDB - ACID Document Database
lasercrabs - Abandoned hybrid singleplayer/multiplayer shooter project formerly known as DECEIVER
Yessql - A .NET document database working on any RDBMS
efcore.pg - Entity Framework Core provider for PostgreSQL
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file
FluentMigrator - Fluent migrations framework for .NET
Streamstone - Event store for Azure Table Storage