dokku-scheduler-kubernetes VS Flynn

Compare dokku-scheduler-kubernetes vs Flynn and see what are their differences.

dokku-scheduler-kubernetes

Scheduler plugin for deploying applications to kubernetes (by dokku)

Flynn

[UNMAINTAINED] A next generation open source platform as a service (PaaS) (by flynn)
Our great sponsors
  • Scout APM - Less time debugging, more time building
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
dokku-scheduler-kubernetes Flynn
4 8
117 7,923
0.9% -
4.0 2.9
3 months ago 9 months ago
Shell Go
MIT License BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

dokku-scheduler-kubernetes

Posts with mentions or reviews of dokku-scheduler-kubernetes. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-14.

Flynn

Posts with mentions or reviews of Flynn. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-31.
  • A Foolish Consistency: Consul at Fly.io
    2 projects | news.ycombinator.com | 31 Mar 2022
    > we are indeed writing a new orchestration system in Go, called `flyd`.

    I know it's just a wild coincidence, but I couldn't help but be reminded of https://github.com/flynn/flynn

  • Show HN: Coolify v2 An open-source and self-hostable Heroku/Netlify alternative
    10 projects | news.ycombinator.com | 30 Mar 2022
    I love these projects and I'll definitely look into it more later. At the same time, I think it would be hard for me to want to leave Kubernetes. K8s isn't something that I love, but it's something that I know works and will continue to be supported in some fashion. I've seen Flynn (https://github.com/flynn/flynn) EOL. I've seen Docker Swarm's future be a bit hazy. I've seen Porter decide to put pretty restrictive limits on their free tier (though it is open source). I've seen Dokku lose steam and then pick up again - but still not be a solution for more than one server.

    I love the idea of something that will Just Work, but a lot of stuff doesn't handle the parts I care about the most. Will my one-click PostgreSQL have a couple replicas in my cluster? Will it launch pg-backrest so I can have it backed up to S3? Will it deal with secret storage so I can just add my secrets in the UI and then have my apps grab those secrets as environment vars? Will it fail-over nicely?

    Coolify looks really cool and I do want to check it out for real later (probably over the weekend to be realistic). However, it seems like it's single-server (for now) and that seems less compelling for me at the moment. It looks like you're planning on K8s support which would just be wonderful.

    Part of me wishes I could get a much simplified UI for K8s. I use Lens at the moment and while it's very good, it doesn't really smooth over the rough bits of K8s, just kinda organizes and presents them. K8s isn't as bad as a lot of people say once you get past the pain of learning. Still, it misses the mark if what you just want a few simple things Heroku-style instead of every bell and whistle. Small users don't care about ingress, they just want their app to be accessible. Small users aren't interested in namespaces or storage classes or roles. Sure, it's important for K8s to support storage classes for large users who might have all sorts of opinions on how they want their data stored. For a small user, you often just want it stored on the local disk.

    Likewise, I think there's a reasonably small set of things people often want to run. For example, the databases Coolify supports (MongoDB, MySQL, PostgreSQL, CouchDB, RedisDB) are probably what 95% of people want. There are K8s operators to run them, but like K8s itself it can often be "here's every knob we could think of, we documented 80% of them, now go write some yaml." Heroku lets me deploy PostgreSQL without that. Why can't I get something a bit more slimmed down like Heroku on K8s - so that if I need the additional power in the future, I can get my hands on it.

    I'd even love it if this hypothetical K8s Heroku could commit the yaml it is going to apply to a GitHub repository for me so I can easily track infrastructure changes. It would even let people become more comfortable with K8s as they saw the changes they were making in the UI show up as commits in a repository.

    I think the point of this rambling is that Coolify is kinda what people want from one perspective - something that seems nice and friendly and handle the cases that the vast majority of people need solved. However, it lacks the critical mass of K8s which can always leave its future in doubt (it looks like there are two of you on this project and open source can take a toll on people) and without high-availability/multi-server it feels a bit lacking for what so many people are looking for in a self-hosted Heroku. Coolify feels like what I'm looking for - I just want it with high-availability and the possibility of continuing on even if the project shuts down (because I can just use an underlying K8s layer, not because it's open source and I could become the new maintainer).

    It feels like there's two camps that don't talk to each other: awesome UX people who know what people want and people building solutions that companies want while scaling up (but end up with a bit of a UX mess).

  • RIP Flynn.io
    1 project | reddit.com/r/patient_hackernews | 28 Feb 2021
    1 project | reddit.com/r/hackernews | 28 Feb 2021
    15 projects | news.ycombinator.com | 28 Feb 2021
    As others have mentioned, the current site (README.md) says very little about what Flynn is.

    You can see a version of the repo and README.md, just before it became unmaintained, here:

    https://github.com/flynn/flynn/tree/2c20757de8b32a40ba06f7e5...

    IMHO it would have been much better if the maintainers had added the "Flynn is Unmaintained" information to the top of the README.md rather than removing all the existing information. I'll submit a GitHub issue suggesting it.

    A plea to project maintainers in general: Please include enough information in your top-level README (or README.md, or README.whatever) so that someone who has never heard of your project can find get a good overview. I've also seen READMEs that only discuss the most recent changes. That's fine for readers who have already been following the project, but not for a more general audience.

    15 projects | news.ycombinator.com | 28 Feb 2021
    15 projects | news.ycombinator.com | 28 Feb 2021
  • Flynn is no longer being developed
    1 project | news.ycombinator.com | 18 Feb 2021

What are some alternatives?

When comparing dokku-scheduler-kubernetes and Flynn you can also consider the following projects:

kubernetes - Production-Grade Container Scheduling and Management

Gogs - Gogs is a painless self-hosted Git service

tsuru - Yet another script to install Tsuru and its dependencies.

Apache Mesos - Apache Mesos

Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications

Gitea - Git with a cup of tea, painless self-hosted git service

Openshift Origin - Conformance test suite for OpenShift

Moby - Moby Project - a collaborative project for the container ecosystem to assemble container-based systems

s3gof3r - Fast, concurrent, streaming access to Amazon S3, including gof3r, a CLI. http://godoc.org/github.com/rlmcpherson/s3gof3r

Hey - HTTP load generator, ApacheBench (ab) replacement

gonative - Build Go Toolchains /w native libs for cross-compilation