I'm working on a side project called dFlow, which is a PaaS (platform-as-a-service) solution that builds on the open-source tool dokku. I want to open a discussion about whether I should integrate Kubernetes or k3s into my project or if it might be better to keep it simple and avoid it altogether.
Many lightweight PaaS tools I've observed don't use Kubernetes or k3s; instead, they run Docker containers on individual servers or use Docker Swarm. This approach makes sense because a lot of smaller teams and solo developers aren't looking for the complexity that comes with orchestrated environments like Kubernetes. They prefer flexibility and ease. Plus, if a project needs to scale later on, moving from a Docker setup to Kubernetes isn't that difficult with the right resources.
As I continue to develop dFlow, I want to ensure the project remains user-friendly while supporting multi-tenant workflows without needing Kubernetes or Swarm. So, I'm at a crossroads where I'm questioning whether I should keep my "no-k8s" approach and focus on user experience and multi-tenancy or consider adding Kubernetes integration or even a hosted option for users who don't want to manage their own servers.
I'd love to get your thoughts on whether I should stay the course or shift my focus!
1 Answer
It really seems like you’re focusing on a crowd that prefers not to deal with Kubernetes, which means you probably already have your answer. Focus on building the features that your users need instead of what you think they might want.
I disagree! While it’s important to listen to customers, sometimes you need to build the features that add real value based on your understanding of their needs, even if they don't ask for them.