Does Application Integration supports these protocols and how?

[ahitankar]

Hi,

I have a simple question like does GCP's Application Integration supports these protocols?

REST/HTTP

SOAP

gRPC

GraphQL

JMS

Webhook

Websocket

Event-Driven Asynchronous Communication (Async API)

I know of the Http/Rest that it supports. It also supports JMS,Websocket. Just curious about the SOAP, gRPC, GraphQL. If they so then how's the configuration for these 3 protocols.

Thanks

[AlexET]

Hi @ahitankar, just wanted to acknowledge your question—still no responses yet, but we’ll make sure it gets noticed and invite others to help out.

[AldoMeneses86]

@ahitankar 

Application Integration in Google Cloud supports a variety of protocols to facilitate seamless communication and data exchange between different applications. Some of the key protocols supported include:

• REST (Representational State Transfer): A widely adopted architectural style for designing and developing web services. It relies on standard HTTP methods (GET, POST, PUT, DELETE) to interact with resources.
• gRPC (Google Remote Procedure Call): A high-performance, open-source framework for developing efficient and scalable RPC systems. It uses Protocol Buffers for efficient data serialization.
• Pub/Sub / JMS  /Event-Driven Integration: A real-time messaging service that allows for asynchronous communication between applications. It enables event-driven architectures and facilitates the decoupling of applications.
• HTTP (Hypertext Transfer Protocol): The foundation of data communication for the World Wide Web. It defines how messages are formatted and transmitted over the network.
• HTTPS (Hypertext Transfer Protocol Secure): An encrypted version of HTTP that ensures secure communication over the internet.

[maloosatyam]

While REST, SOAP and GraphQL are different request formats all are nothing but HTTP requests. SOAP is POST on HTTP & GraphQL will be GET or POST on HTTP

[hartmann]

@maloosatyam is correct, most of these protocols can be utilized/invoked via the HTTP connector. For SOAP specifically, we have an XSL Transformer: https://cloud.google.com/application-integration/docs/reference/data-transformer-reference/xml-funct... which should make it easy to transform/validate/etc the request to something per your SOAP service's expectation

For gRPC specifically what is your use case - are you calling a back end microservice? I am wondering if you could use something like the REST connector, and call into Apigee (who acts as a wrapper to the gRPC service): https://github.com/apigee/external-callout

[ahitankar]

Hi @AldoMeneses86, @maloosatyam and @hartmann - Thanks for giving the nice info...What about Websocket and Webhook?

[maloosatyam]

For Webhook use the HTTP POST and you can use Apigee for websocket https://cloud.google.com/apigee/docs/api-platform/develop/websocket-config