You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To improve the performance of KubeEdge dashboard, we would like to introduce a BFF (Backend for Frontend) layer. It serves as a middle layer to handle the communication between the dashboard and the KubeEdge API, providing a more efficient, secure, and maintainable solution.
There are several features that we would like to implement in the BBF layer:
The BFF layer will improve the performance of KubeEdge dashboard by reducing the number of requests sent to the KubeEdge API and optimizing the data processing.
The text was updated successfully, but these errors were encountered:
Hello @ghosind ,
I am Harshita, excited to start contributing , I have expertise in backend technologies like Node.js, Golang, and MongoDB, alongside frontend frameworks like React and Redux. I can work on this idea by leveraging my experience in designing scalable backend systems and implementing efficient APIs to develop the BFF layer for the KubeEdge dashboard. My focus will be on integrating keink, handling errors and retries seamlessly, and optimizing data pre-processing to enhance the dashboard's performance, security, and maintainability
Hi @ghosind ,
The projects sound great !! I had been working with the required technologies for almost 2 years now. Is there any pre-requisite tasks to be completed for this project ?
Thank you
What would you like to be added?
To improve the performance of KubeEdge dashboard, we would like to introduce a BFF (Backend for Frontend) layer. It serves as a middle layer to handle the communication between the dashboard and the KubeEdge API, providing a more efficient, secure, and maintainable solution.
There are several features that we would like to implement in the BBF layer:
Why is this needed?
The BFF layer will improve the performance of KubeEdge dashboard by reducing the number of requests sent to the KubeEdge API and optimizing the data processing.
The text was updated successfully, but these errors were encountered: