tailcall

Must Have: - Strong understanding of GraphQL and related technologies. - Previous experience in a developer relations, advocacy, or evangelism role. - Proven ability to present technical concepts in a clear and engaging manner. - Active participation in relevant tech communities. Nice to Have: - Experience with Rust or other modern programming languages. - Familiarity with web proxies, networking, and related technologies. - Established online presence (e.g., on GitHub, Twitter, blogs). - Contributor to Tailcall - https://github.com/tailcallhq/tailcall Additional Requirements: - Passionate about connecting with developers and understanding their needs. - Positive attitude towards collaboration and community building. - Self-driven and adaptable to the evolving needs of the project. Share your linkedin/twitter profile here and we will con

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

This sure seems very interesting. Have you written the GraphQL 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.

The reasons mentioned above is exactly why we started Tailcall. https://github.com/tailcallhq/tailcall GraphQL community is quite small and fragmented. Mostly composed of frontend engineers who are focused on improving dev-ex with APIs. It would benefit the ecosystem, if people with a system's background or platform engineering background could get involved. Fix various aspects of performance, security and maintenance.