-
octosql
OctoSQL is a query tool that allows you to join, analyse and transform data from multiple databases and file formats using SQL.
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
wundergraph
WunderGraph is a Backend for Frontend Framework to optimize frontend, fullstack and backend developer workflows through API Composition.
-
go-sqlite3-stdlib
A standard library for mattn/go-sqlite3 including best-effort date parsing, url parsing, math/string functions, and stats aggregation functions
Hey, congrats on the journey!
Especially on the community building aspect, it's really impressive that you've been able to spark so many communities on various platforms (Reddit, GitHub, Discord, etc.)!
On a more technical note, since dsq is based on the "load it into SQLite and query it from there" architecture, have you considered integrating with the plugin ecosystems of other existing projects, like Datasette[0]? It looks like a way to add a lot of value to your tools without much work.
Just curious, cause I'm thinking about doing something similar for OctoSQL[1] (write an adapter for the rich library of plugins Steampipe[2] has).
Overall I think tools like this are very hard to monetize, because right now they're just a fairly niche use case, between - as you mentioned - full blown data analytics platforms and observability query systems. Especially since if you need the analytics a lot, you'll probably have time to integrate it into your warehouse. Do you have any thoughts on that?
[0]:https://datasette.io
[1]:https://github.com/cube2222/octosql
[2]:https://steampipe.io
Hey, congrats on the journey!
Especially on the community building aspect, it's really impressive that you've been able to spark so many communities on various platforms (Reddit, GitHub, Discord, etc.)!
On a more technical note, since dsq is based on the "load it into SQLite and query it from there" architecture, have you considered integrating with the plugin ecosystems of other existing projects, like Datasette[0]? It looks like a way to add a lot of value to your tools without much work.
Just curious, cause I'm thinking about doing something similar for OctoSQL[1] (write an adapter for the rich library of plugins Steampipe[2] has).
Overall I think tools like this are very hard to monetize, because right now they're just a fairly niche use case, between - as you mentioned - full blown data analytics platforms and observability query systems. Especially since if you need the analytics a lot, you'll probably have time to integrate it into your warehouse. Do you have any thoughts on that?
[0]:https://datasette.io
[1]:https://github.com/cube2222/octosql
[2]:https://steampipe.io
Hey, congrats on the journey!
Especially on the community building aspect, it's really impressive that you've been able to spark so many communities on various platforms (Reddit, GitHub, Discord, etc.)!
On a more technical note, since dsq is based on the "load it into SQLite and query it from there" architecture, have you considered integrating with the plugin ecosystems of other existing projects, like Datasette[0]? It looks like a way to add a lot of value to your tools without much work.
Just curious, cause I'm thinking about doing something similar for OctoSQL[1] (write an adapter for the rich library of plugins Steampipe[2] has).
Overall I think tools like this are very hard to monetize, because right now they're just a fairly niche use case, between - as you mentioned - full blown data analytics platforms and observability query systems. Especially since if you need the analytics a lot, you'll probably have time to integrate it into your warehouse. Do you have any thoughts on that?
[0]:https://datasette.io
[1]:https://github.com/cube2222/octosql
[2]:https://steampipe.io
Thanks for this writeup, I can relate 100%, especially the part on the supportive spouse. I've built WunderGraph (https://wundergraph.com/) as a solo-dev for multiple years until I reached a similar point like you. It's weird to say, but my wife kind of accepted that I'd work on weekends between 1-3 pm when the kids sleep. What helped me get out of this "solo-time-drain-thing" was to find the right Co-Founders to help me. I've found a really nice guy to help me with Marketing, and another one who helped me develop the Product. "If you want to go fast, go alone. If you want to go far, find a team." I hope you can find some way of financing so that you can push through this wall. For me, it was working a full time job and building WunderGraph at night and on the weekends, but it's making you age quickly. I wish you the best for your future.
Hey Kuba!
> Especially on the community building aspect, it's really impressive that you've been able to spark so many communities on various platforms (Reddit, GitHub, Discord, etc.)!
Yeah it's been so cool to see so many people come together, hobbyists and professionals.
> On a more technical note, since dsq is based on the "load it into SQLite and query it from there" architecture, have you considered integrating with the plugin ecosystems of other existing projects based on that same architecture, like Datasette[0]? It seems like a way to add a lot of value to your tools without much work.
Interesting idea! I haven't looked into Datasette too much. And I haven't thought about plugins too much either. The most I've done is extend the SQLite standard library [0] and I hope to continue growing that. I'd be curious to hear what specifically people like from Datasette they'd like to see in dsq.
> On a more commercial note, overall I think tools like this are very hard to monetize, because right now they're just a fairly niche use case, between - as you mentioned - full blown data analytics platforms and observability query systems, as well as standard unix tools. Especially since if you need the analytics a lot, you'll probably have time to integrate it into your preferred analytics solution (like BigQuery). Do you have any thoughts on that?
My idea was always to focus on smaller and less mature organizations, probably ones that have been around for 10+ years. They aren't using BigQuery, they prefer to host everything themselves, and they don't yet realize there are tools like DataStation that they can easily run to make analytics easier.
I've worked at a bunch of companies like this so I know the market exists. Actually I have been surprised how many people outside of this market showed up in the DataStation community. I've seen Googlers, MS-ers, modern startups, data science teams show up interested in DataStation compared to what they're already using.
For me it's just been a matter of time (and funding) to build out the product to serve these communities commercially as a SaaS or enterprise product.
[0] https://github.com/multiprocessio/go-sqlite3-stdlib
You have a broken link to your repo - I believe https://github.com/multiprcessio/datastation-documentation should be https://github.com/multiprocessio/datastation-documentation