8 ms·
MRSK: Deploy web apps anywhere
- deedubaya 4y agoI’m using it to deploy a dockerized nodejs app, it works great!
- hardwaresofton 4y agoBtw Traefik is an excellent proxy: https://traefik.io/traefik https://traefik.io/traefik Far too few people know about it IMO
- razemio 4y agoReally? I believe it is one of the most known proxies besides Nginx and apache. Especially in docker environments.
- whitemary 4y agoYes, really. I was interviewing last year and used it in one of the projects on my resume. Almost nobody knew what it was. In fact, exactly 1 out of 25-30 people I discussed the project with knew what Traefik was..
- razemio 4y agoSad days. I am fairly active in the self hosting scene. Traefik is a superstar there right after caddy.
- yunohn 4y ago> fairly active in the self hosting scene Though that is probably why - Traefik is popular for self-hosting, while Caddy is more generally mainstream.
- ricardobeat 4y agoIsn't it the opposite? Traefik is more common in the enterprise as an nginx replacement for k8s, while Caddy is easier to setup and great for self-hosting - I've never seen it used in enterprise environments.
- yunohn 4y agoYou could be right - I’ve only heard of Traefik in self-hosting contexts.
- tarellel 4y agoI wish I could upvote this more! Traefik is absolutely amazing! And it seems like in the development community every wants to use nginx. But in my experience traefik is absolutely perfect for proxying with container deployed applications.
- berkle4455 4y agoI want to learn Traefik but it yet again has another overly verbose config file. They could learn a lot from caddy. Is it better enough to deal with learning a new DSL?
- conqrr 4y agoI'd stick to Caddy. I deprecated my old traefik reverse proxy and tls config which took me days to get right earlier mostly due to my lack of understanding, but the config and DSL is a little tricky too. With Caddy its literally 4 lines of code. Sane defaults are really powerful. I don't have any comments on performance etc as these are hobby projects, I did like traefik's dashboard though.
- hardwaresofton 4y agoI find traefik does really well in dynamic, more complex environments (like kubernetes). It also really depends on what you want out of the proxy. Probably makes sense to try caddy first for simpler use cases and graduate to traefik if you find some features you want to have (like l4 traffic that isn’t alpha:beta)
- mattjaynes 4y agoI'm one of the many who hadn't heard of Traefic until MRSK mentioned it. The marketing seems very (overly?) targetted at cloud microservices and container-specific tech[1]. Is that just marketing, or is it really not a good fit for monoliths on bare-metal? [1] https://github.com/traefik/traefik https://github.com/traefik/traefik "Traefik (pronounced traffic) is a modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components (Docker, Swarm mode, Kubernetes, Consul, Etcd, Rancher v2, Amazon ECS, ...) and configures itself automatically and dynamically. Pointing Traefik at your orchestrator should be the only configuration step you need."
- klabb3 4y agoI’ve been trying out many reverse proxies for stateful, low-traffic websocket connections, but unfortunately they all eat so much ram. Even nginx, with tuning, use at least 10x ram/conn of a well tuned naked uWebSocket deployment with TLS. Traefik was much more ram hungry than nginx, and iirc Caddy as well (at least 2 goroutines per conn). It’s probably fine (and worth it) for the vast majority of request-response web apps, but all of these extra layers have a cost. And that’s still nothing compared to the overhead of say k8s with all bells and whistles. Anyway, as someone who’s been out of the loop on backend for many years, I am quite shocked at the level of resource waste, even among the projects with a strong reputation. You always hear the complaints about frontend bloat, but these days backend seem to have caught up.
- hardwaresofton 4y agoYeah I’m personally of the opinion that the performance loss for regular web services is worth it 99% of the time. RAM is cheap, human time is not. That said I definitely believe your characterization of resource hunger between nginx and traefik. You are the second person to mention using websockets for requests in as many days… How do you deal with scale out? Sticky cookie routing seems like almost a requirement if you don’t want to deploy a redis-alike. Also just out of curiosity, do you use hyper-express[0]? [0]: https://github.com/kartikk221/hyper-express https://github.com/kartikk221/hyper-express
- emptysongglass 4y agoI am not a fan of the 37signals model. Basecamp is a terrible product. Last I used it with a partner, it still didn't support inline code highlighting. They're very opinionated about everything but I don't see their opinions driving good products. Kubernetes has been getting better with every release. I'd advise companies thinking of doing it better to implement their improvements to K8s directly so it can become a scalable, easy to use standard for everyone. 37signals is part of a contingent of reactionary developers and you can see this in HEY and now MRSK. It's reactionary without delivering real innovative value.
- yunohn 4y agoUpvoted this, because opinions about an opinionated product should be allowed. Fully agree that 37Signals’ products are very opinionated and often missing crucial features. I can see that they fulfil some use-cases, but could be more mainstream.
- LapsangGuzzler 4y agoI don’t have a problem with opinions on products, but urging people to “do x instead of y because standards” is such an intellectually lazy take, especially when the party being criticized has led development on some of the most influential open source projects in history. I’d love to see OP do anything as remotely influential in the industry as DHH.
- yunohn 4y ago> I’d love to see OP do anything as remotely influential in the industry as DHH. I vastly prefer their appeal to standards over your appeal to authority.
- mirekrusin 4y agoTheir standard is rational thinking though first principle decomposition - if it still holds through their evaluation, it'll stay as standard, otherwise it's not a standard from their PoV.
- sickcodebruh 4y agoMRSK is like something pulled straight from my dreams. Longtime Capistrano user, loves Docker for reproducible environments but still hasn’t mastered using it in prod because I’m a dinosaur who just wants servers and a load balancer. I’m gearing up to deploy a Nextjs project in the next few months and while I appreciate the claims of Function this and Edge that, I feel infinitely more comfortable with a couple small server instances, especially early on when my focus should be testing my product, not optimizing my cloud infrastructure for scale that might never be needed. I’m excited to give MRSK a shot and feel grateful to live in a time when there are so many good choices.
- lobstrosity420 4y ago> especially early on when my focus should be testing my product, not optimizing my cloud infrastructure for scale that might never be needed Not to mention vendor lock in, something that really needs to be talked about more with this new wave of function this and edge that.
- PragmaticPulp 4y agoAvoiding vendor lock-in always sounds nice in theoretical discussions, but in practice it needs to be weighed against the cost of additional development time. In the past decade I’ve been on several teams that went out of their way to avoid vendor lock-in by refusing to use platform service offerings. Every single time it was a complete waste of time. We could have saved a lot of time by embracing platform offerings and then trying to port to a different vendor only if necessary.
- breakfastduck 4y agoYou are absolutely correct here for most businesses. Howvever, there are many companies working within heavily regulated sectors that unfortunately need to be able to evidence a rapid ability to switch platforms AND exactly where data is stored and processed. As such using very specific offerings in cloud providers is unfortunately not always an option. Something that is portable, even at expense of complexity or available dev time, becomes a non negotiable.
- sea-gold 4y agoRelated discussion: "MRSK vs Fly.io" (162 comments): https://news.ycombinator.com/item?id=35263886 https://news.ycombinator.com/item?id=35263886 Also here is the MRSK introduction blog post: https://world.hey.com/dhh/introducing-mrsk-9330a267 https://world.hey.com/dhh/introducing-mrsk-9330a267
- mati365 4y agoWhy not use just podman systemd service (with quadlet)?
- emptysea 4y agoI don't think podman systemd integration handles blue/green style handoff, but pod man's integration is pretty nice. Really painful to manually call a docker container from systemd normally, lots of edge cases to manage
- revskill 4y agoThe confusing part is, how to put a load balancer in front of those deployed servers ?
- lbotos 4y agoIf your “host servers” are known (say 4 backends) you set up the balancer and point it to the 4 host IPs. If you are dynamically allocating host servers and needing to register them with the LB you should probably consider K8s? This is designed for a “more stable” world: Have some hosts. Have an LB. Deploy containers to those hosts. Avoid superfluous k8s complexity that you don’t need.
- leetrout 4y agoI don't think you need K8S for that. Any decent load balancer (LB) is going to have some concept of origin configuration that weights routing with various algorithms and health checks. You would just update the config in the LB when you bring a new origin online.
- alex_suzuki 4y agoI’m also interested in this setup and have so far only had experience using HAProxy. Any alternatives HN can recommend? (software)
- turtlebits 4y agoLoad balancing isn't part of MRSK - all public clouds offer them, Digitalocean does as well. Or DIY with Haproxy, Nginx, Traefik, etc.
- datadeft 4y agoSorry one of the key part of deploying web applications is not part of the offering.
- cschep 4y agoHe sets up a load balancer in his demo video? Did you watch it?
- mlangenberg 4y agoCan MRSK be used to manage deploying applications that are distributed as Docker images, such as Adguard Home? I see there is support for ‘accessories’ such as Redis. What if I only want to deploy an image and skip building a Dockerfile and pushing it to a registry?
- mr_ndrsn 4y agoYup, use an accessory for that. I used it to setup a Minecraft server for our last company meetup. I agree, there should be a way to have the primary app be an image that doesn’t get built/pushed.
- c-hendricks 4y agoNice, this reminds me of something from a few years ago: https://github.com/mikew/b3cmd-server https://github.com/mikew/b3cmd-server https://github.com/mikew/b3cmd https://github.com/mikew/b3cmd This used docker-compose + git.
- emkrawiec 4y agolooks nice and tries to solve a problem i had a while ago: how to deploy a small dockerized app to a cheap vm with declarative deploy (like k8s) but without k8s. anyone know a similiar tool?
- simo7 4y agoYou can ship your local docker context to a remote host and build/run your containers there. All the docker commands you typically run locally you can run on the remote host. https://www.docker.com/blog/how-to-deploy-on-remote-docker-hosts-with-docker-compose/ https://www.docker.com/blog/how-to-deploy-on-remote-docker-h...
- emkrawiec 4y agothanks! I was a little bit confused at first because I've always taken docker compose as a tool mainly for spinning up dev environments. But I read mentioned article and it looks perfectly valid for single host deployments. One thing which bothered me is how i manage container versions usually made with hashes but all you need is to either make sth like a compose template like file which would have a version placeholder or specify production compose configuration on top of the default one. https://stackoverflow.com/a/71194294 https://stackoverflow.com/a/71194294 https://docs.docker.com/compose/production/ https://docs.docker.com/compose/production/
- doublepg23 4y agoAm I missing the problem with just docker-compose?
- deleted 4y ago[deleted]
- m00dy 4y ago""" gem install mrsk """ you lost me right in there.
- siliconc0w 4y agoHe mentioned partitioning bare-metal into VMs (which is a good idea, containers aren't a great security boundary) but it doesn't look like MRSK does that (yet?). I can see using this to deploy on DO or Hetzner to save a few bucks vs Render or Amplify- but on bare metal you're giving up a pretty amazing ecosystem these days. Ie. if you want to run stateful things like databases, logging/monitoring, NFS, object storage, persistent disks, complex networking, etc it's going to be miles easier to manage that w/ k8s. Even for that bare-metal/vm-partitioning goal above, there is a k8s runtime (kata-containers) which will automatically run containers on lightweight vms and handle all the plumbing to and from K8s. Plus if your mid-size SaaS wants to sell to the whales you're going to need compliance and security best practices that are much easier to implement and enforce w/ k8s. Finally, there are also lighter weight distributions these days to make it less painful to run yourself. That said, I do appreciate the 37signals philosophy of having such strong opinions they craft their own tools and I also applaud leaving the cloud for bare metal. Even if you need the burst capacity you can provision your base-load on bare-metal and burst to the cloud when needed.
- ricardobeat 4y agoI had the impression k8s is still not recommended to run a DB or any kind of persistence. Are any large companies doing that in production? Regarding logging, object storage, how does kubernetes help? You'll have to implement these regardless of the underlying container infra.
- nosvince 4y agoOndat does that, a bunch of people are using them. And Akamai acquired them, probably to scale their model
- seabrookmx 4y agoYes. Lots of companies run things like ElasticSearch and Cassandra in Kubernetes. And even sharded RDBMS's are doable now thanks to projects like Vitess, which famously underpinned YouTube. Basically if there's a mature k8s operator for the DB in question, it's pretty straight forward. The "use containers/k8s for stateless stuff only" approach is very dated.
- tezza 4y agoDo not get wedded to that name… Maersk will be in touch to gently ask that MRSK desist using their trademark.
- dangoor 4y agoIANAL, but my understanding is that trademark law is based on the idea of avoiding confusion in the marketplace. It's possible to have similarly named products in completely different industries without violating trademark law because they won't confuse potential buyers of the product. THAT said, I'm not sure I personally would take the gamble!
- satvikpendem 4y agoA terminal had to change the name from Terminix to Tilix due to trademark issues, even though one is a terminal and the other is a pest killer. https://github.com/gnunn1/tilix/issues/815 https://github.com/gnunn1/tilix/issues/815
- dangoor 4y agoOh yeah, that's a good point. Given my understanding of trademarks, I'm not sure Terminix's claim would hold up in court, _but_ that's irrelevant because people don't generally want to go to court. I doubt 37signals would go to court to keep the MRSK name.
- 6t6t6t6 4y agoI wouldn't be so sure knowing the stubbornness of DHH...
- xrd 4y agoThis looks to me like something that has 5% of the features of dokku. If you want a slimmed down dokku that seems great. But I'm wondering if I love dokku why I would choose this. What am I missing? The switching to live containers and proxy integration seems like table stakes these days. Is traefik that much better than nginx in all cases? And, dokku just works with almost any kind of web app (regardless of the language) i throw at it. It's amazing for just git cloning something, create a dokku app and new git remote and then just push and see if it works, which it does almost all the time. It's super fun to experiment with something new and just see what happens.
- ricardobeat 4y agoMRSK is a bit more focused on deployment and server management: it only needs SSH access to configure a server and deploy your application. Dokku still requires managing/installing servers manually.
- Cyph0n 4y agoSo it’s trying to both tackle provisioning and deployment at the same time? Why not just use more powerful tools for each role - e.g., provision with Ansible and deploy with Dokku?
- josegonzalez 4y agoDokku Maintainer here. Is the issue that you only need to `gem install mrsk` locally vs running our bootstrap script to install Dokku on a remote server? I'm not sure what the difference is maintenance-wise between Dokku and MRSK, as at the end of the day you still have a server you need to maintain/upgrade for both products.
- axelthegerman 4y agoused dokku too but faced a couple of issues over time including very slow deploys for some reason. also fubdamentally dokku is single server whereas MRSK is multi-server. not that I need that but worth pointing out as a difference
- rileymichael 4y agoIt’s not immediately obvious to me how this differs from something like ansible which people have been using for years for basic deployment topologies. What am I missing? edit: after looking a bit closer, I think it’s a bit misleading to call what this is doing “zero downtime”. as far as I can tell, your services are essentially going to be unresponsive until they start, which can be brutal for slow starting ones (and that’s assuming they start successfully)
- deleted 4y ago[deleted]
- Thaxll 4y agoIt's 2023 and a dev deploying an app needs to know the physical IPs of a machine it's going to deploy on, really good design.
- rudasn 4y agoIts in the same repo, yes, but don't have to care about it, just as you may not care about Ci artifacts or editor config files, or gitignore files or whatever. That info has to live somewhere, and in the same repo as the code doesn't sound that bad.
- 6t6t6t6 4y agoThe value proposition of MRSK is to deploy servers on a few machines that you physically own. Their focus is not on serverless-cloud-native-infinite-scaling.
- x3haloed 4y agoUgh. This still isn't quite what I want. I can't stand Docker. It's so damn heavy. All I want is something like the following: - Sandboxed applications - With an agent to control which ones run on a machine - A GUI to easily observe and manage deployments - Infra-as-code using a sensible file format (anything but YAML) I imagine this working best with VM-based runtimes like .NET and WASM. The ability to control resources consumption isn't there yet, but I don't see why you couldn't have a runtime that gives fine-grained controls over sandboxing and resource consumption. This idea came about from observing discourse on replacing conventional hypervisors with WASM/WASI. Forget Docker. Forget OCI. Forget Kubernetes/SWARM. We just need a simple system for orchestrating apps that are already VMs.
- MuffinFlavored 4y agoyou hate Docker, OCI, and yaml? kind of hipster?
- WrtCdEvrydy 4y agoCaprover comes close to this. You can pack your app into a zip file and upload it with a special file or choose pre-packaged apps.
- sr-latch 4y agoI find Docker running a full Linux userspace a little bloated. Thankfully there are distroless base images(https://github.com/GoogleContainerTools/distroless https://github.com/GoogleContainerTools/distroless). Haven't done service dev in a while, so I don't really have experience with this, but it looks promising.
- sampullman 4y agoDistroless is great for things that compile to static binaries, I use it for Rust apps. For anything that pulls in heavy dependencies, having a package manager is convenient (alpine, debian-slim).
- stareatgoats 4y agoThis should probably be seen in the context of this: https://twitter.com/dhh/status/1613508201953038337 https://twitter.com/dhh/status/1613508201953038337
- satvikpendem 4y agoHow does it compare to Coolify?
- tylerjl 4y agoSlightly off-topic, but my ChatGPT instincts always tend to fire whenever I read copy that concludes with the formula, “Ultimately…” or “Overall…”. I wonder how much (if any) of this landing page was GPT generated.
- throwawaaarrgh 4y agoLike most things system, this can be replaced with regular existing tools and a shell script. You will gain a lot more valuable knowledge and experience by learning how to use existing systems, rather than picking up yet another magic unicorn tool that promises you the moon but won't help you when it breaks. Do you plan to be doing this job for the next 10 years? Then set aside the time to learn system tools and scripting. The time investment, however long it takes, will pay itself off many times over, guaranteed.
- switchbak 4y agoOr, you could use existing tools and patterns so the next person picking up your project has even the slightest chance of being productive. Yes you can glue things together with existing stuff. Let's not pretend that cgroups+namespaces+dnsmasq (or whatever) tech is actually a better solution. It might be "simple" via some metric, but it's yet another ad-hoc piece of engineering that has to be understood and maintained. I've seen this at a former job, and it was an absolutely horrible idea.
- throwawaaarrgh 4y agoSure. But if you're going to use a "real" system that can be adopted by others, you might as well use the most popular, well known, well funded, well supported tool out there. Using this "Capistrano alternative" won't be familiar for people that come after, and they'll spend just as much time learning it as learning a janky shell script, except the janky shell script is at least tailored to your use case.
- switchbak 4y agoI'd agree with that too. I'd be open to something truly simple (Nomad perhaps?) over K8S in some scenarios, but if I'm going to take a gamble, it's going to have to be a lot simpler to provide enough benefit on taking a chance on a less popular piece of tech.
- solatic 4y agoI'm not going to claim that Kubernetes on bare-metal is easy, but it's certainly doable. And it's worth doing, because of all the ecosystem work that's been built up on Kubernetes over the last several years, everything from observability, to workload scaling, to database management, to multi-datacenter service networking. Switching to something new (MRSK), means throwing that out. How is MRSK 10x better to make it worth losing the ecosystem? Of course you need full-time admins to babysit your bare-metal Kubernetes clusters. But if you're running bare metal, you made the financial decision that (cost of full-time InfraOps Engineers + cost of bare-metal servers <<< cost of IaaS cloud). So you're already paying for full-time InfraOpEng. In this day and age, is it really reasonable not to expect them to know Kubernetes cluster management as well?
- ksajadi 4y agoMRSK was designed to handle deployment of 37Signals products to bare metal servers and it does that well. However when it comes to deploying to cloud it falls short by a lot: start with dealing with cloud native load balancers (ELB, ALB, …) as services come and go, or persistent storage requirement for state full services and much more you’ll need to take care of yourself. I think it’s important to remember that MRSK is a bare metal department tool and not really designed for the cloud, as per the creators’ statements. https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47e0 https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47...
- majkinetor 4y agoWhile I realy love DHH and his blog, and noticed MRSK while he was writing about their cloud exit (very nice story, highly recomended) I have to wonder, why would I use this instead of Nomad? It supports similar usecase but Nomad is more mature, activelly improved, supports non-docker environments and is cross-platform.
- sureglymop 4y agoI use Qemu/KVM VMs and then deploy Apps with Docker Compose and Ansible (including Traefik). Would this make my workflow obsolete or easier?