7 ms·
3000 users? You can save the data on disk and not worry about it. Get a vultr 5 dollar micro instance. I don't know why all these engineer driven businesses foc
by ilrwbwrkhv 4y ago
3000 users? You can save the data on disk and not worry about it. Get a vultr 5 dollar micro instance. I don't know why all these engineer driven businesses focus on the wrong things. You don't need fly.io. Of course they will tell you you need them, I don't blame them. But fly.io or kubernetes should always be done by a migration team which you can hire once you have insane profits. Yes profits, the other tiny detail most businesses are missing these days.
- mrkurt 4y agoI won't tell you you need Fly.io. I am offended you'd put us in the same bucket as kubernetes though, rude.
- jabo 4y agoIt's interesting to see how being in the same league as kubernetes could either be considered a compliment or an insult depending on who you ask!
- GiorgioG 4y agoK8s is a complexity sinkhole for 99% of companies. It's an insult.
- alfalfasprout 4y agoIt's funny how we spend SO much time dealing with K8s related nuances and limitations. In practice, I'm not so sure anymore even for a large enterprise that K8s actually simplifies things in any way or adds more robustness.
- mountainriver 4y agoUh huh here we go. What other tool do you propose for running many containers with dependencies on one another? Or why should I target a bunch of different cloud APIs to make my tool consumable when I can target one?
- capableweb 4y agoFirst question: why you need many containers for just 3000 users? That should easily run on a cheap VPS unless you're doing something ridiculously complex. Why target any cloud APIs at all if your product have a small amount of users? You don't need to scale up/down fast at if you're just at 3000 users. Throw it on a Linux box, write a systemd service and be done with it.
- mountainriver 4y agoI'm not talking about 3k users, he said 99% of use cases
- capableweb 4y ago> 99% of companies Most companies have small amount of users and don't have rapidly shrinking/growing user bases, meaning their infrastructure need is not rapidly shrinking/growing neither, in most cases. Hence, Kubernetes being accidental complexity most people can do without, rather than necessary complexity.
- mountainriver 4y agoEh I don't have the numbers, but every company I've worked for has had lots of users. Their infra wasn't shrinking or growing much to make good use of k8s. Mainly they needed to link a bunch of runtime containers together built by different teams. I get why people say k8s is complex, but there really isn't another great option for running a containerized service based architecture, maybe nomad
- httgp 4y agoNomad is pretty fantastic!
- mountainriver 4y agoYeah nomad is okay but not as functional as k8s (yet)
- ipaddr 4y agoYou've inspired me to give it a chance.
- ilrwbwrkhv 4y agoFair enough. You guys are definitely a breath of fresh air compared to kubernetes. And we already use you guys although Cloudflare is pitching us their Workers pretty heavily.
- joshxyz 4y agoHaha, damn we need better one-liner analogies on these to easily discern the both in the future. If k8s is ____, fly is ____. I cant even compare fly to heroku, almost the same but different underneath.
- jahsome 4y ago
- bsnnkv 4y ago> You can save the data on disk and not worry about it. I one day aspire to have the cajones of ilrwbwrkhv. For the reference of other potential solo devs, if done right, Fly.io will still be cheaper than the Vultr 5 dollar micro instance (or equivalent) with an incomparably better DX.
- ipaddr 4y agoWith the threat of a much higher bill if done wrong. That $2.50 vultr instance provides a lot more like 20 gigs of storage nevermind security of a fixed bill. You might be able to save a little, you might pay a lot more. Hedge your bet and use vultr.
- bsnnkv 4y agoI generally agree, though I would add that I think this depends a lot on the skill set and technical background of the person. My gut feeling is that if someone is going to struggle with optimizing for a relatively fixed target like Fly (the billing is extremely predictable compared to some other offerings out there, if not completely fixed), the chances are that they won't be cut out to do double time taking on what is effectively a Linux sysadmin role.[1] [1] I may be completely wrong
- deznu 4y agoOr just have billing alerts...
- pclmulqdq 4y agoBilling alerts can tell you exactly when you have spent 4 figures after the fact. Using a VPS prevents 4-figure bills. Actual billing caps are very hard for cloud providers to implement with the HA distributed systems clouds use for billing, and would carry a significant performance cost. Alerts are the best you can do if you take the variable costs.
- deznu 4y ago
- deleted 4y ago[deleted]
- wooque 4y ago
- bsnnkv 4y agoI am happy to engage in discussion with critical comments made in good faith. This comment however, with its unnecessary ad-hominem attacks, seems particularly mean-spirited. For this reason, I have flagged your comment.
- dimgl 4y ago110% this. For a small business with a small amount of users, I always suggest to *use the simplest thing that'll save you the most time and money to deploy your service*.
- judge2020 4y agoEven if it would be best for the company, "managing VMs" is less impressive on a resume than "set up auto-scaling and server IAM utilizing fly.io and Tailscale".
- mbreese 4y agoI’m not sure resume-driven development is a trend we should embrace. (Even if we all acknowledge that it is one motivation for many tech fads). Honestly, if this is on a resume the next question should be — tell me why you needed such a system…
- nisegami 4y agoThat's why I advocate for MDD instead, short for Magpie Driven Development. Just as Magpies like their shiny trinkets, I like my shiny frameworks.
- jsyolo 4y agoYou can save the data on disk and not worry about it. Like in sqlite or something like json files?
- pclmulqdq 4y agoFilesystems have a lot more flexibility than just storing JSON or databases. A notes app probably should just store markdown files with some links between each other, and a few small databases for indexes.
- sgtnoodle 4y agoYou could also store base64 encoded blobs in yaml, or implement a self-modifying bash script key-value store you call into from a shell. Those are the only other options before it's time to move everything over to into the cloud.