Lock in quality if you try gRPC
Microservices architecture. Many organizations today recognize it enables faster and easier software changes over more traditional monoliths.
Microservices have become the backbone for how organizations develop cloud-native applications – programs that run independently in containers designed for cloud computing architectures. Companies of every size are rethinking how they scale and develop APIs, which means they use multiple protocols to address challenges they didn’t have a few years ago.
At SmartBear, we make it our mission to meet developers where they work, with the tools that are going to enable them to be successful. Following on the heels of our successful launch of support for Apache Kafka and AsyncAPI, we are excited to announce we have added API testing support for the popular, open source Remote Procedure Call framework, gRPC.
As you may already know, gRPC takes a more contemporary approach to the traditional remote procedure call (RPC) protocol.
Why Is gRPC Here? Where Does It Work?
Since its release in 2016, gRPC has gained traction due to its ability to support multiple languages and client and server bindings. Though initially developed and used by Google, it is now adopted by some of the largest enterprises in the world, including Netflix, Square, IBM, and Cisco. The protocol is open source and part of Google’s sponsorship for the Cloud Native Computing Foundation (CNCF) ecosystem of cloud-native offerings.
SmartBear has a long history of support for open source communities, including our patronage for Swagger.io, SOAPUI.org and Cucumber.io .
gRPCs usage of HTTP/2 and Protocol Buffers allows it to work well in many situations. The Protocol Buffers (protobufs) allow for increased performance due to the use of a binary format for the encoded messages. The messages are faster to exchange and less CPU intensive. This means that servers as well as clients, like mobile devices and IoT, can benefit from the smaller message size.
To Reach #1, Stay Open
In addition to decreased message size, gRPC also provides support for communication between services even if they are written in different languages. With the continued growth of microservices, many companies are looking to gRPC as the protocol of choice for internal systems.
ReadyAPI ensures high quality, performance, and security in all APIs regardless of type – from legacy SOAP services, to microservices powered by Kafka and mainstream REST services, to cutting-edge IoT use cases leveraging MQTT and the performance advantages seen with gRPC.
At SmartBear, our focus on being the number one API development platform has driven us to expand protocol support not only for our ReadyAPI testing product, but also as part of the API design process using SwaggerHub.
We see the launch of gRPC testing support as non-negotiable when it comes to being protocol agnostic. At SmartBear we ensure that regardless of the protocol, our customers have the development and testing capabilities they need to “deliver high quality software.”
Get in the Know
To learn more about how users can leverage gRPC and other newly added features available in ReadyAPI 3.20, visit the What’s New page: https://support.smartbear.com/readyapi/docs/general-info/whats-new.html.
SmartBear plans to support new protocols, schemas, and definitions in future ReadyAPI releases.
To learn more, register for the webinar on ReadyAPI’s support for gRPC on Wednesday, February 9, 2022 at: https://smartbear.com/resources/webinars/grpc-and-readyapi/.