190 karma · joined June 20, 2017
Also, for configuring all sort of credentials for libraries, e.g. AWS, WandB, HuggingFace, etc.
As to the topic, IMO, there is a contradiction. The only way to handle big data is to divide it into chunks that aren’t expensive to query. In that sense, no data is "big" as long as it’s handled properly.
Also, about big data being only a problem for 1 percent of companies: it's a ridiculous argument implying that big data was supposed to be a problem for everyone.
I personally don’t see the point behind the article, with all due respect to the author.
I also see many awk experts here who have never been in charge of building enterprise data pipelines.
Are there any reads on whether it’s worth at all to get in to YC these days?
- For our hosted version, we use Litestream; we lack a UI for accessing data.
Disclaimer: I’m the creator of dstack.
To share more context:
dstack is an open-source tool designed for managing AI infrastructure across various cloud platforms. It's lighter and more specifically geared towards AI tasks compared to Kubernetes. Due to its support for multiple cloud providers, dstack is frequently used to access on-demand and spot GPUs across multiple clouds.
To democratize access to GPUs, and to streamline the process of managing multiple clouds, we introduce dstack Sky, a managed service that enables users to access GPUs from multiple providers through dstack – without needing an account in each cloud provider.
We launched dstack Sky today on Product Hunt: https://www.producthunt.com/posts/dstack-sky
Happy to hear feedback, and answer questions!
Finally, I believe simple configuration can coexist with code.
P.S.: At dstack, we are building an open-source platform to manage AI infra – a more lightweight and AI-friendly alternative to Kubernetes.
FTR, we integrate dstack with Kubernetes too - already [1] But our native cloud integrations can be a lot more efficient. For example, when it comes to auto-scaling - this part is in work