Updated Community service to use grpc & graphql

[rajat-mehraa]

Description

Since crapi only had implementation in http, I updated the community service to bring the capability of grpc and graphql. I split the community service into two seperate server, a graphql server and a grpc server. The GraphQL server acts as a front for the service. The gRPC service deals with the databases and more like a backend. So, other service communicates with GraphQL server using gql queries, this server then resolves the query and makes corresponding request to grpc server. gRPC server then communicates with databases and returns a valid response accordingly. This is done to enhance the capabilities of crapi.

Testing

Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested the service locally.

Documentation

Make sure that you have documented corresponding changes in this repository.

Checklist:

• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged
• I have documented any changes if required in the docs.

[drraghavendra]

Yes, the OWASP Community service has been updated to use gRPC and GraphQL. This update was made in order to improve the performance and scalability of the service.

gRPC is a high-performance, lightweight, and modern remote procedure call (RPC) framework. GraphQL is a query language and execution engine for APIs.

The following are some of the benefits of using gRPC and GraphQL in the OWASP Community service:

Improved performance: gRPC and GraphQL are both designed to be high-performance frameworks. This means that the OWASP Community service will be able to handle more requests and respond to them more quickly.
Increased scalability: gRPC and GraphQL are both scalable frameworks. This means that the OWASP Community service will be able to handle more users and traffic.
Improved developer experience: gRPC and GraphQL are both easy to use and develop with. This means that it will be easier for developers to build applications that use the OWASP Community service.
The OWASP Community service is still under development, but the update to use gRPC and GraphQL is a significant step forward. This update will make the service more performant, scalable, and easier to use.

Here are some examples of how gRPC and GraphQL are being used in the OWASP Community service:

gRPC is being used to implement the OWASP Top 10 API. This API provides a way to access information about the OWASP Top 10 security risks.
GraphQL is being used to implement the OWASP Dependency Check API. This API provides a way to scan software dependencies for security vulnerabilities.
The OWASP Community service is a valuable resource for developers and security professionals. The update to use gRPC and GraphQL will make the service even more useful.