aptakube VS tailcall

Are you specifically looking for a free Kubernetes GUI?

If you’re open to commercial options, have a look at what Aptakube (https://aptakube.com) can do.

One feature that sets it apart from other UIs is connecting to multiple clusters simultaneously and seeing all resources in a single table.

Disclaimer: I’m the author

During my previous job, when we were migrating to Kubernetes I couldn’t really find a GUI app that I liked, and most importantly, that could connect to multiple clusters simultaneously. We had 6 clusters and having to switch context constantly was annoying

I ended up building one [1] to use myself, shared with a few people and they loved it. I asked if they’d pay for it and to my surprise, a lot of people said yes. I’ve put up a website and a “pre-order” button with a regressive monthly discount. Sales were going up month after month, and a few months later I decided to quit my job to go all in on it.

Today, I’m averaging on ~€5k/mo from this app, but I’m still doing some part time freelancing, as well as building other products that are not as successful, but are making >€1000/mo

The latest one is open source, privacy friendly analytics for apps [2] that I’m still very actively working on. This is my current “side project” as the previous side project became my main job :)

There’s also an open source upvote site [3] that I haven’t had much time to work on lately, but still generating $$ monthly.

[1] https://aptakube.com

In case you're into Kubernetes, check out Aptakube, a Kubernetes Desktop Client built with Tauri 😊

Aptakube is GUI application for Kubernetes that uses the same Kubeconfig files we mentioned above and can connect to multiple clusters at the same time. It essentially presents all your Kubernetes resources as if it was a single clusters. We invite you to try it out free today 😊

I have two projects, combined doing ~€1500/mo

https://fider.io - an open source alternative to UserVoice. I started this one 6 years ago to learn Go and React. I’ve seen thousands of instances out there being self hosted, so I started a cloud hosting to those who don’t want to manage it themselves.

https://aptakube.com - Desktop Client for Kubernetes. This is very recent, launch was 2 weeks ago, so it’s only starting to get some traction now.

I’m leaving my job to go full time indie hacker now, wish me luck!

I'm giving a shot on https://aptakube.com. not OSS, but so far has been a great alternative to lens and k9s. The guy behind it made a thread here a while ago.

Thanks again for sharing your feedback! In case you have more, you can drop them here or add them to https://github.com/aptakube/aptakube

Actually, you might want to check out https://tailcall.run (Disclaimer: I am the core maintainer of the project)

It's an open-source API Orchestrator, in other words "a Zapier for APIs". If you find it interesting, hit our discord channel to learn more about it.

Tailcall is building something similar in that regard. The idea is to allow developers to specify their orchestration requirements using a DSL and then behind the scenes generate an ultra high performance backend for GraphQL. The query could span over REST, GRPC and other GraphQL services. Check it out — https://github.com/tailcallhq/tailcall

GraphQL will save you from embarrassing errors on the client and improve performance for sure. My recommendation is — Build API and expose them using REST or GRPC. Use a solution like https://tailcall.run/ to create a GraphQL facade on top of it for your clients to consume.

layer by hand? Have you tried https://github.com/tailcallhq/tailcall

With tailcall, you can quickly bootstrap a GraphQL service on top of existing APIs. I would love to collaborate on this and help you on board.

Hi, I am the founder of https://tailcall.run. I have personally built and used GraphQL at a massive scale (100M rpm, 1K APIs, 100s services). I believe have a fair understanding of the problem it solves, as well as its pitfalls. We built Tailcall because we realized that manually writing a GraphQL service is inefficient and doesn't scale well. Our main learning was that APIs should be built and operated independently, regardless of how they are consumed.

GraphQL should also be considered as a client-side abstraction and architecturally positioned closer to the client than to the server. In this context, the client could be a mobile app, a website, or even another service querying data from an external or internal data source. As a client-side abstraction, the responsibility of maintenance should lie with the consumer of the APIs, not the producer. All these learnings have helped us architect Tailcall as it is today. Tailcall provides a DSL that allows consumers of the API to configure how they would want the schema to look. Behind the scenes, Tailcall automatically orchestrates the APIs to generate a unified graphQL endpoint. Once configured it can be deployed on a typical server, but semantically still being a piece of the client/API Consumer.

This way of looking at graphQL considers federation as an anti-pattern. GraphQL Federation pushes graphQL towards the server side or more specifically the API producer. This new layer of abstraction also adds significant levels of slowness & complexity in architecture. We started with the problem of clients consuming APIs and the need to compose them, but ended up using a solution that's composing "Graphs". That's not necessarily wrong, but it feels like an overkill for the core problem the organization starts with which is — API Composition.

However, we understand that this might not be relatable for smaller organizations and various others who have been working with GraphQL for a long or probably have a different take on it. I would love to hear your thoughts!

Some of the questions we had were —

Do you prefer to handwrite a graphQL API or, use an open-source solution that could auto-generate a GraphQL endpoint on top of your existing API?

What are your thoughts on GraphQL in general — like, hate, neutral? Does it solve a big problem in your company? Have you tried TRPC as an alternative?

Do you think federation is the future? Based on what you learned, do you think Tailcall is a good design?

Have you considered using https://tailcall.run