dapr VS Nomad

Azure Container Apps is a container orchestration platform for deploying modern applications and microservices. With Azure Container Apps you can deploy your containerized apps without the need to take on the overhead of managing the infrastructure of the underlying systems. This service is still in preview, but provides you with the ability to use your preferred language or framework to build microservices with support for Distributed Application Runtime (Dapr). There's also scaling of your containers with Kubernetes Event-Driven Autoscaling (KEDA).

If you are looking for a unified way to build this across different clouds, you could look into DAPR https://dapr.io/

Take a look at DAPR if you are looking for a conceptual Queues, Storage, Pub Sub etc without being tied to any particular infrastructure. https://dapr.io/

This sounds like something you can do with Dapr (https://dapr.io/) It's a microservice architecture that was developed by Microsoft i think and now open-source. It has build in support for communication between services. I don't know your architecture/landscape or the requirements, but maybe this could work for you. If not, yeah queues could work. Setup a listener on startup for the specific queue and you should be good. Keep scaling in mind, I think there was a limit to the number of listeners is possible on a queue (1 per partition or something)

Dapr is a set of APIs that makes it easy for developers to write distributed applications. Dapr runs as a sidecar process next to an application, whether on Kubernetes or any other environment.

Think i agree that the tooling is a little behind for .net and gRPC but it isn't bad. Are you also cutting the monolith into smaller pieces you might want to look at https://dapr.io/

I guess https://dapr.io/ could also be considered a contender in that space, though the developer experience is not as polished as next.js (yet?).

Very cool project. It reminds me a bit of https://dapr.io (even though they're obviously quite different).

One tiny note on the docs - I found it surprisingly hard to find the github repo for the project listed in the docs. I was expecting to find a GitHub link under contributing but only saw a slack channel. I eventually spotted a link in the Roadmap section.

https://dapr.io/ might be a fit sometimes

Projects like Dapr aim to be the Holy Grail for application development. Their goal is to help developers build resilient services that run in the cloud. By codifying best practices for building microservices into independent and agnostic building blocks that can be used only if necessary, they allow services to be built using any language or framework and run anywhere.

Must be hashicorp's nomad: https://www.nomadproject.io/

That's a false statement as far as the technical aspects are concerned (Swarm is still usable and supported), but is a true statement when you look at the social aspects (Kubernetes won the container wars and now even Nomad is uncommon to run into).

Right now the company i'm in uses Swarm in a lot of places due to its simplicity (Compose file support) and low resource usage - Swarm hits the sweet spot when it comes to getting started with container orchestration and doing so without needing multiple people to wrangle the technical complexity of Kubernetes, or large VMs to deal with its resource usage, at least in on prem environments.

In combination with Portainer (https://www.portainer.io/) it's perhaps one of the best ways to get things done, when you expect everything to just work and aren't doing something too advanced (think along the lines of 10 servers, rather than 100, which is probably most of the deployments out there).

I actually wrote about some of its advantages in my blog post, "Docker Swarm over Kubernetes": https://blog.kronis.dev/articles/docker-swarm-over-kubernete...

That said, if there are any good options to replace Swarm, it has to either be Hashicorp Nomad (https://www.nomadproject.io/) which is a really nice platform, especially when coupled with Consul (https://www.consul.io/), as long as you can get past the weirdness of HCL. Alternatively, it has to be K3s (https://k3s.io/), which gives you Kubernetes without the insane bloat and hardware usage.

I actually benchmarked K3s against Docker Swarm in similar app deployments: 1 leader server, 2 follower servers, running a Ruby on Rails app and an ingress, while they're under load testing by K6 (https://k6.io/). I was attempting to see whether COVID contract tracking with GPS would be viable as far as the system load goes in languages with high abstraction level, here's more info about that: https://blog.kronis.dev/articles/covid-19-contact-tracing-wi...

Honestly, the results were pretty close - on the follower servers, the overhead of the orchestrator agents were a few percent (K3s being heavier, but a few dozen MB here or there not being too relevant), whereas the bigger differences were in the leader components, where K3s was heavier almost by a factor of two, which isn't too much when you consider how lightweight Swarm is (there was a difference of a few hundred MB) and the CPU usage was reasonably close in both of the cases as well. Sadly, the text of the paper is in Latvian, so it's probably of no use to anyone, but i advise you to do your own benchmarks! Being a student, i couldn't afford many servers then, so it's probably a good idea to benchmark those with more servers.

Of note, on those VPSes (4 GB of RAM, single core), the full Kubernetes wouldn't even start, whereas at work, trying to get the resources for also running Rancher on top of a "full" Kubernetes cluster (e.g. RKE) can also take needlessly long due to the backlash from ops. Also, personally i find the Compose syntax to be far easier to deal with, rather than the amalgamation that Kubernetes uses, Helm probably shouldn't even be a thing if the deployment descriptors weren't so bloated. Just look at this: https://docs.docker.com/compose/compose-file/compose-file-v3...

In short:

  - Docker Swarm is pretty good when you're starting out with containers and is reasonably stable and easy to use

Also if you don’t want to look at kube then check out Nomad. https://www.nomadproject.io/

Hahaha sure: https://www.nomadproject.io it’s by HashiCorp.

Yeah, this pains me too. Here's a relevant issue to keep an eye on:

https://github.com/hashicorp/nomad/issues/3854

I've used an nginx-based S3 proxy in the past to get around this. Not ideal but it works.

At Lob, we currently use Convox as our deployment platform, a “roll your own Platform-as-a-Service” that you can install to handle container orchestration on AWS’s ECS (Elastic Container Service). Convox is showing its age and this year we began the process of replacing Convox with HashiCorp’s Nomad, a flexible workload orchestrator to deploy and manage our containers on AWS.