-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Build an API Gateway Based on CloudWeGo Projects #75
Comments
Project Name: API Gateway |
|
Project Name: Svb_2.0 Author Yip Sin Hang, Niu wen jia. Our emails are [email protected] and [email protected]. Repo: https://github.com/simbayippy/OrbitalxTikTok Documentation: here Description: A High performance API Gateway that is able to dynamically update any service updates in IDL file during run time, supporting the 4 different types of generic clients of Kitex. Additional attempts made for the protojson_codec was made - close but still a work in progress The full scope of our project can be found in our documentation process. |
Project Name: Godzilla Gateway (Inspired from the Kong API Gateway)Authors: Boh Jie Qi, Winson Zheng, our emails are [email protected] and [email protected] respectively. Repo: https://github.com/jieqiboh/Godzilla-Gateway Documentation: This page provides links to our entire submission, including the system design document, relevant setup videos, and github repositories Description:
Our API Gateway also provides the following features:
We also made our own custom benchmarking tool using Apache Bench that is able to measure key metrics like TP99 and QPS for our gateway, and made a cool logo :) |
Project Name: API Gateway Authors: Gabriel Chua, Loh Jian Rong. Our emails are [email protected] and [email protected] respectively. Repo: https://github.com/jianrong7/orbital-23 Documentation: This page provides links to our entire submission, including the system design document, cloud deployment documentation, as well as testing. Description: A working API Gateway that is able to support server-side updates to the IDL, and service registration using Consul. It supports the JSON Generic Call function of the Kitex framework. |
Project Name: CloudWeGo-API-Gateway Authors: Repo: https://github.com/RashawnXue/CloudWeGo-API-Gateway Documentation: You can find the documents of the project in README.md and this page Description:
|
Project Name: Hertz API-gateway Authors:
Repo: https://github.com/lar0129/hertz-APIgateway Documentation:
Description:
|
Project Name: Cloudwego Apigateway Authors:
Repo: https://github.com/sherry-500/apigateway Documentation:
Description: The project implemented an API Gateway with two CloudWeGo' s frameworks: Hertz and Kitex. In this project, the API gateway accepts HTTP requests with json payloads and routes them to the respective services, retrieves the responses, and returns them to the clients. It also supports IDL management, which allows to hot update IDL. |
Project Name: API_Gateway
Github: https://github.com/yashma-sonara/API_Gateway Documentation: System Design Document Demo: Demo Video Description: This project is an API Gateway implementation that serves as a centralized entry point for accessing and managing multiple backend services. Our project includes:
|
Project Name: cloudwego-api-gateway Authors: Github: https://github.com/iksars/cloudwego-api-gateway Documentation: docs Description: Our project implements the following functions 2.lruCache optimization for generic call client 3.idl management platform(frontend & backend) which support to curd IDL file and manage service interface 4.api gateway support IDL dynamically update |
Project Name: Authors: TwinDagger email: [email protected] Github: https://github.com/iksars/cloudwego-api-gateway Documentation: apidoc Description: Here are the features and technologies used in our project: |
Goal
The primary goal of this proposal is to implement a demo API Gateway on Hertz which accepts HTTP requests encoded in JSON format and uses the Generic-Call feature of Kitex to translate these requests into Thrift binary format requests. The API Gateway will then forward the request to one of the backend RPC servers discovered from the registry center.
Requirements and Deliverables
You're encouraged to post your implementation here for others' reference.
Template:
The text was updated successfully, but these errors were encountered: