Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Dev] Use gRPC in the .NET Web App Alert UI and Alert-API microservice (ALERTS-API and Web APP UI client) #64

Open
CESARDELATORRE opened this issue Feb 16, 2023 · 0 comments
Open

[Dev] Use gRPC in the .NET Web App Alert UI and Alert-API microservice (ALERTS-API and Web APP UI client) #64

CESARDELATORRE opened this issue Feb 16, 2023 · 0 comments
Assignees
@pabravil @Javipercor @dsaezvil
Labels
issue Bug, but it's not breaking the app P3 (Long-term and much less priority) Features and improvements to have in the backlog, still to be triaged and prioritied.

Comments

@CESARDELATORRE
Copy link
Contributor

@dsaezvil
We need to use gRPC to improve perf and minimize latency.
Only the Python services are currently using gRPC.
The .NET microervices (ALERTS-API and Web APP) need to use gRPC, as agreed from the begining of the project.
@CESARDELATORRE CESARDELATORRE added the issue Bug, but it's not breaking the app label Feb 16, 2023
@CESARDELATORRE CESARDELATORRE changed the title [Dev] Use gRPC in the .NET microservices (ALERTS-API and Web APP UI client) [Dev] Use gRPC in the .NET Web App Alert UI and Alert-API microservice (ALERTS-API and Web APP UI client) Feb 17, 2023
@CESARDELATORRE CESARDELATORRE added the P1 (High priority) High priority means fixes/featureswe should be working in DEV branch asap.Also, docs if high prio. label Feb 17, 2023
@CESARDELATORRE CESARDELATORRE added P3 (Long-term and much less priority) Features and improvements to have in the backlog, still to be triaged and prioritied. and removed P1 (High priority) High priority means fixes/featureswe should be working in DEV branch asap.Also, docs if high prio. labels Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pabravil pabravil

@Javipercor Javipercor

@dsaezvil dsaezvil

Labels
issue Bug, but it's not breaking the app P3 (Long-term and much less priority) Features and improvements to have in the backlog, still to be triaged and prioritied.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@CESARDELATORRE @pabravil @Javipercor @dsaezvil