Live data from Hacker News

I am building a cloud

crawshaw.io

491–500 of 589 posts

Re: I am building a cloud

#491

Earlier quoted context omitted.

Call me old fashion but I prefer tools like Dokploy that make deployment across different VPS extremely easy. Dokploy allows me to utilize my home media server, using local instances of forgejo to deploy code, to great effect. k8s appears to be a corporate welfare jobs program where trillion dollar multinational monopolistic companies are the only ones who can collectively spend 100s of millions sustaining. Since mos…

I took over tech for a POS company some years ago. They were a .net shop with about 80 developers, less than 200 concurrent connections, 6 figures spend cloud, and 0 nines uptime with a super traditional setup. Point being, it's not the tools the causes the probem.

Just curious, are you still looking for developers? Asking as someone who is a developer that works with POS systems.

Re: I am building a cloud

#492
post #348

Earlier quoted context omitted.

Just as a quick aside, I tried Coolify, Dokploy, Dockge, and Komodo, and if you're trying to do a Heroku-style PaaS, Dokploy is really good. Hands down the best UX for delivering apps & databases. It's too bad about the licensing. (e.g. OIDC + audit logs behind a paid enterprise license.) Coolify is full of features, but the UX suffers and they had a nasty breaking bug at one point (related to Traefik if you want to…

If you're open, love to get your thoughts on https://miren.dev . We've doing similar things, but leaning into the small team aspects of these systems, along with giving folks an optional cloud tie in to help with auth, etc.

How is it monetized? I read something about open core and paying for additional services I think. What are those and where can I find them?

Re: I am building a cloud

#493

Earlier quoted context omitted.

There's one extra process that takes up a tiny bit of CPU and memory. For that, you get an immutable host, simple configuration, a minimal SBOM, a distributable set of your dependencies, x-platform for dev, etc.

Yes but NixOS does all of these things already, without the process overhead

Nix wraps your process in namespaces and seccomp?

Re: I am building a cloud

#494
post #396

Earlier quoted context omitted.

This is why there's an endless cycle of shitty SaaS with slow APIs and high downtime. People keep thinking that scale is something you can just add later.

What's a more reasonable general approach then? Let's say you're a team of 1-3 technical people building something as an MVP, but don't necessarily want to throw everything away and rewrite or re-architect if it gets traction. What are your day 1 decisions that let you scale later without over-engineering early? I'm not disagreeing with you btw. I genuinely don't know a "right" answer here.

I don't think there's a right answer, you need to sit down and try to think about these problems upfront. What will scaling look like? What decisions will you regret? Make the guesses you can, but don't ignore scale or performance.

Re: I am building a cloud

#495
People who don't understand the software bloat cycle are doomed to repeat it.

Lean software -> missing features users want -> add features over time -> bloated mess -> we need a smaller rewrite -> Lean software -> ...

Re: I am building a cloud

#496

People who don't understand the software bloat cycle are doomed to repeat it. Lean software -> missing features users want -> add features over time -> bloated mess -> we need a smaller rewrite -> Lean software -> ...

True. The solution is to make a different piece of software customised for each person.

Re: I am building a cloud

#497

Earlier quoted context omitted.

K8s isn't even hard! My team of three manages everything on K8s and we spend ~0 minutes per week on it. Write a script to generate some YAML files, stick it in a CI pipeline, and it's basically fire-and-forget. You're going to want most of what K8s has anyway: blue-green deployments, some way to specify how many replicas you want, health checks, etc. The initial setup cost is annoying if you've never done it before,…

Are you using a service like GKE, or running your own cluster? I've set up clusters "from scratch" in dev environments to get familiar with it.

We do both: managed Kubernetes when it's available (AWS, Nebius, others), but for some hardware vendors they just give us raw machines and we self-host K3s on their nodes. We're an open-source LLM inference company so we're basically always scrambling for GPUs wherever we can get them, which means we need to be fairly scrappy with what we support while still having a semi-sane interface for ourselves internally. Kubernetes makes that pretty easy: onboarding a new vendor takes ~minutes, and then everything Just Works and we can interact with the pool of compute the same way we do every other pool since the K8s API is standard, with all of our built-in prod monitoring tools immediately set up and running.

That being said I love exe.dev and have been a happy customer since launch. It's a different use case but they do an amazing job at it. Very, very easy personal cloud dev box. But K8s is very very good too, just for production workloads rather than personal ones!

Re: I am building a cloud

#498

People who don't understand the software bloat cycle are doomed to repeat it. Lean software -> missing features users want -> add features over time -> bloated mess -> we need a smaller rewrite -> Lean software -> ...

It's more of a spiral than a loop, usually the reboot either flops or gets something crucial right and progresses to the point where it challenges the incumbent.

Re: I am building a cloud

#499

Earlier quoted context omitted.

Yes but NixOS does all of these things already, without the process overhead

Nix wraps your process in namespaces and seccomp?

Not by default but tools like agent-sandbox.nix (bwrap, seccomp) or other nixpak (just bwrap but more popular) can provide those capabilities if you want in a fairly simple interface

Re: I am building a cloud

#500

There's a common conversation that goes on around AI: some people swear its a complete waste of time and total boondoggle, some that its a good tool when used correctly, and others that its the future and nothing else matters. I see the same thing happen with Kubernetes. I've run clusters from various sizes for about half a decade now. I've never once had an incident that wasn't caused by the product itself. I recall…

Seems like this can be applied to an increasingly large pool of subjects, where things are polarized by default and having a moderate/indifferent opinion is unusual. For example, I thought of US politics while reading your comment

I thought of how people view hot pepper sauce
Post reply on HN