521–530 of 589 posts
You should do it in Europe, so much demand for European clouds and very weak offerings.
US company doing cloud in Europe changes nothing because of the CLOUD Act: https://en.wikipedia.org/wiki/CLOUD_Act
Earlier quoted context omitted.
Docker is great development tooling (still some rough edges, of course). Docker Compose is good for running things on a single server as well. Docker Swarm and Hashicorp Nomad are good for multi-server setups. Kubernetes is... enterprise and I guess there's a scale where it makes sense. K3s and similar sort of fill the gap, but I guess it's a matter of what you know and prefer at that point. Throw on Portainer on a s…
> Docker Swarm IS that a thing still? > Kubernetes is... enterprise I would contest that. Its complex, but not enterprise. Nomad is a great tool for running processes on things. The problem is attaching loadbalancers/reverse proxies to those processes requires engineering. It comes for "free" with k8s with ingress controllers.
Earlier quoted context omitted.
Neat service. Website doesn't provide enough information for me to trust any workloads to it. Not clear where the underlying infrastructure is, what security guarantees I get, etc.
Thanks for the feedback. Ill improve it. In the meanwhile, there are more technical details on this blog post: https://shellbox.dev/blog/race-to-the-bottom.html
Running Shellbox 24/7 is ~25% cheaper than Exe, with 2x storage but 50% of RAM. Exe seems to provide additional features (which I don't need). Not presenting this information upfront and in an easily digestible format makes me suspicious.
I dig the overall aesthetic and may give Shellbox v2 a try.
Earlier quoted context omitted.
> the average devops knows k8s and will slap it onto anything they see This is certainly the case from all the third person accounts I hear. Online. I never actually met a single one that is like that, if anything, those same people are the ones that are first to tell me about their Hetzner setups.
DevOps here. The trouble is that we are literally expected to do this everywhere we go. I've personally advocated for approaches which use say, a pair of dedicated servers, or VMs as in GPs example. If you want it outside of AWS/GCP/Azure, you're regarded as a crazy person. If you don't adopt "best practices" (as defined by vendors) then management are scared. Management very often trust the sales and marketing depar…
…IBM
…Microsoft
…AWS.”
> Making Kubernetes good is inherently impossible, a project in putting (admittedly high quality) lipstick on a pig. So well put, my good sir, this describes exactly my feelings with k8s. It always starts off all good with just managing a couple of containers to run your web app. Then before you know it, the devops folks have decided that they need to put a gazillion other services and an entire software-defined netw…
I don't get it, I think that k8s is the best software written since win95. It redefines computing in the same way IMHO. I have some experience in working with k8s on prod and I loved every moment of it. I'm definitely missing something.
knowing when and when not to use k8s, is also a skill
Earlier quoted context omitted.
> the average devops knows k8s If you'd know Kubernetes, you know not to use it. I say that as someone who used to do consulting for it. The reality is that yet again "making money" completely collides with efficient, quality, sane productive work. For me one of the main reasons to leave that space is that I couldn't really deal with the fact that my work collides with a client's success. That said I have helped to g…
I think one big problem is that using microservice architecture doesn't mean that literally everything has to be a "microservice". if you don't truly need granual scaling (i.e. your "app" doesn't get a bunch of asymmetric loads across different paths), then you can just have more monolithic "microservices" until they need to be split up imo this should achieve a nice balance?
SOAs have most utility in scaling teams, not software: creating independent services allows autonomy to independent teams if they apply a few simple patterns for good SOA.
Earlier quoted context omitted.
Then why can't we put a wrapper onto systemd and make that into a light weight k8s?
Systemd is on the wrong layer here. You need something that can set your machine up, like docker.
Tech like Flatpak or Snap is closer to Docker than "machines" are — except that Docker has local, virtualized networking built-in as the IPC layer.
Starting a digital ocean droplet is a single curl call. Starting a hetzner server is as well. Their api’s are completely fine and known to llm’s.
Why would agents learn exe’s way of setting up / deploying / binding to ports / auth, rather than just ssh’ing into a vm..?
Earlier quoted context omitted.
What images are you running that you'd need the latest version up after just a minute?
When I push new images via CI, I want it to go in production immediately. Like Heroku/Render/Dokku
Maybe you meant to say "automatically" instead of "immediately"? Because if you really mean "immediately" then there is still plenty of low-hanging fruit to be had.