A high-performance GraphQL Platform (by tailcallhq)

Tailcall Alternatives

Similar projects and alternatives to tailcall

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better tailcall alternative or higher similarity.

tailcall reviews and mentions

Posts with mentions or reviews of tailcall. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-19.
  • Developer Relations Engineer [Tailcall]
    2 projects | news.ycombinator.com | 19 Mar 2024
  • Ask HN: Is There a Zapier for APIs?
    3 projects | news.ycombinator.com | 19 Feb 2024
    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.

  • The Ur Programming Language Family
    2 projects | news.ycombinator.com | 27 Jan 2024
    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
  • Ask HN: Would anyone recommend GraphQL over REST for teams just starting up?
    1 project | news.ycombinator.com | 24 Jan 2024
    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.
  • Ask HN: Those making $500/month on side projects in 2024 – Show and tell
    11 projects | news.ycombinator.com | 23 Jan 2024
    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.

  • Ask HN: GraphQL in 2024
    1 project | news.ycombinator.com | 16 Dec 2023
    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?

  • Join Tailcall Mini Hackathon: Win $2000 and a Job Opportunity
    1 project | news.ycombinator.com | 14 Dec 2023
  • Ask HN: What apps have you created for your own use?
    212 projects | news.ycombinator.com | 12 Dec 2023
    Have you considered using https://tailcall.run
  • Kotlin Multiplatform Is Stable and Production-Ready
    2 projects | news.ycombinator.com | 2 Nov 2023
  • TailCall: High-performance API Gateway for GraphQL back ends
    1 project | news.ycombinator.com | 28 Oct 2023
  • A note from our sponsor - SaaSHub
    www.saashub.com | 22 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic tailcall repo stats
7 days ago

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives