#gRPC

[juh-wasnt-deactivated19691231]

just typed into google "java grpc client screaming" and had a good laugh

[govindhtech]

Apigee Extension Processor v1.0: CLB Policy Decision Point

V1.0 Apigee Extension Processor

This powerful new capability increases Apigee's reach and versatility and makes managing and protecting more backend services and modern application architectures easier than ever.

Modern deployers may add Apigee rules to their scalable containerised apps using the Extension Processor's seamless Cloud Run interface.

Additionally, the Extension Processor creates powerful new connections. With gRPC bidirectional streaming, complicated real-time interactions are easy, enabling low-latency, engaging apps. For event-driven systems, the Extension Processor controls and protects Server-Sent Events (SSE), enabling data streaming to clients.

Benefits extend beyond communication standards and application implementation. When used with Google Token Injection rules, the Apigee Extension Processor simplifies safe Google Cloud infrastructure access. Apigee's consistent security architecture lets you connect to and manage Bigtable and Vertex AI for machine learning workloads.

Finally, by connecting to Google's Cloud Load Balancing's advanced traffic management features, the Extension Processor offers unequalled flexibility in routing and controlling various traffic flows. Even complex API landscapes may be managed with this powerful combine.

This blog demonstrates a powerful technique to manage gRPC streaming in Apigee, a major issue in high-performance and real-time systems. gRPC is essential to microservices, however organisations employing Google Cloud's Apigee as an inline proxy (traditional mode) face issues owing to its streaming nature.

Nous will examine how Apigee's data plane may regulate gRPC streaming traffic from the ALB to the Extension Processor. A service extension, also known as a traffic extension, allows efficient administration and routing without passing the gRPC stream through the Apigee gateway.

Read on to learn about this solution's major features, its benefits, and a Cloud Run backend use case.

Overview of Apigee Extension Processor

Cloud Load Balancing may send callouts to Apigee for API administration via the Apigee extender Processor, a powerful traffic extender. Apigee can apply API management policies to requests before the ALB forwards them to user-managed backend services, extending its robust API management capabilities to Cloud Load Balancing workloads.

Infrastructure, Dataflow

Apigee Extension Processor requirements

Apigee Extension Processor setup requires several components. Service Extensions, ALBs, and Apigee instances with Extension Processors are included.

The numerical steps below match the flow diagram's numbered arrows to demonstrate order:

The ALB receives client requests.

The Policy Enforcement Point (PEP) ALB processes traffic. This procedure involves calls to Apigee via the Service Extension (traffic extension).

After receiving the callout, the Apigee Extension Processor, which acts as the Policy Decision Point (PDP), applies API management policies and returns the request back to the ALB.

After processing, the ALB forwards the request to the backend.

The ALB gets the backend service-started response. Before responding to the client, the ALB may utilise the Service Extension to contact Apigee again to enforce policies.

Making gRPC streaming pass-through possible

Apigee, an inline proxy, does not support streaming gRPC, even though many modern apps do. Apigee Extension Processor is handy in this circumstance since it allows the ALB to process streaming gRPC communication and act as the PEP and the Apigee runtime as the PDP.

Important components for Apigee's gRPC streaming pass-through

Using the Apigee Extension Processor for gRPC streaming pass-through requires the following components. Get started with the Apigee Extension Processor has detailed setup instructions.

gRPC streaming backend service: A bidirectional, server, or client streaming service.

The Application Load Balancer (ALB) routes traffic and calls to the Apigee Service Extension for client requests.

One Apigee instance with the Extension Processor enabled: A targetless API proxy is used by an Apigee instance and environment with Extension Processor to process Service Extension communication using ext-proc.

In order to link the ALB and Apigee runtime, a traffic extension (ideally Private Service link (PSC)) is configured.

When configured properly, client to ALB, ALB to Apigee, and ALB to backend may interact.

Apigee secures and manages cloud gRPC streaming services

Imagine a customer creating a high-performance backend service to deliver real-time application logs using gRPC. For scalability and administrative ease, their primary Google Cloud project hosts this backend application on Google Cloud Run. The customer wants a secure API gateway to offer this gRPC streaming service to its clients. They choose Apigee for its API administration capabilities, including authentication, authorisation, rate restriction, and other regulations.

Challenge

Apigee's inline proxy mode doesn't allow gRPC streaming. Typical Apigee installations cannot directly expose the Cloud Run gRPC service for client, server, or bi-di streaming.

Solution

The Apigee Extension Processor bridges gRPC streaming traffic to a Cloud Run backend application in the same Google Cloud project.

A concentrated flow:

Client start

Client applications initiate gRPC streaming requests.

The entry point ALB's public IP address or DNS name is the target of this request.

ALB and Service Extension callout

The ALB receives gRPC streaming requests.

A serverless Network Endpoint Group connects the ALB's backend service to Cloud Run.

The ALB also features a Service Extension (Traffic extension) with an Apigee runtime backend.

The ALB calls this Service Extension for relevant traffic.

Processing Apigee proxy

Service Extensions redirect gRPC requests to Apigee API proxies.

Apigee X proxy implements API management controls. This includes rate limiting, authorisation, and authentication.

No Target Endpoint is defined on the Apigee proxy in this situation.ALB finalises route.

Return to ALB

Since the Apigee proxy has no target, the Service Extension answer returns control to the ALB after policy processing.

Backend routing in Cloud Run by Load Balancer

The ALB maps the gRPC streaming request to the serverless NEG where the Cloud Run service is situated, per its backend service parameters.

ALB manages Cloud Run instance routing.

Managing responses

Request and response flow are similar. The backend starts the ALB to process the response. The ALB may call Apigee for policy enforcement before responding to the client via the Service Extension (traffic extension).

This simplified use case explains how to apply API management policies to gRPC streaming traffic to a Cloud Run application in the same Google Cloud project using the Apigee Extension Processor. The ALB largely routes to Cloud Run using its NEG setup.

Advantages of Apigee Extension Processor for gRPC Streaming

Using the Apigee Extension Processor to backend manage gRPC streaming services brings Apigee's core features to this new platform application, with several benefits:

Extended Apigee's reach

This technique extends Apigee's strong API management tools to gRPC streaming, which the core proxy does not handle natively.

Utilising current investments

Businesses using Apigee for RESTful APIs may now control their gRPC streaming services from Apigee. Even while it requires the Extension Processor, it uses well-known API management techniques and avoids the need for extra tools.

Centralised policymaking

Apigee centralises API management policy creation and implementation. Integrating gRPC streaming via the Extension Processor gives all API endpoints similar governance and security.

Moneymaking potential

Apigee's monetisation features may be utilised for gRPC streaming services. Rate plans in Apigee-customized API solutions let you generate money when gRPC streaming APIs are accessed.

Better visibility and traceability

Despite limited gRPC protocol-level analytics in a pass-through situation, Apigee provides relevant data on streaming service traffic, including connection attempts, error rates, and use trends. Troubleshooting and monitoring require this observability.

Apigee's distributed tracing solutions may help you trace requests in distributed systems utilising gRPC streaming services with end-to-end visibility across apps, services, and databases.

Business intelligence

Apigee API Analytics collects the massive amount of data going through your load balancer and provides UI visualisation or offline data analysis. This data helps businesses make smart decisions, identify performance bottlenecks, and understand usage trends.

These benefits show that the Apigee Extension Processor can offer essential API management functionalities to Google Cloud's gRPC streaming services.

Looking Ahead

Apigee Extension Processor enhances Apigee's functionality. Apigee's policy enforcement will eventually be available on all gateways. The Apigee runtime will serve as the Policy Decision Point (PDP) and the ext-proc protocol will allow many Envoy-based load balancers and gateways to act as Policy Enforcement Points. Due to this innovation, organisations will be better able to manage and protect their digital assets in more varied situations.

[gleerpconfessions]

My name is Kes and a really, really long time ago I mainly played Destery Dawson for the Hazel Run RP. I was very close with Ken and pretty close with Inez. I miss you both dearly and hope life is treating you well. If this gets posted I hope you all reach out if you see this. To anyone I hurt, I’m truly sorry. For my contribution to petty drama, I’m regretful and owe my sincerest apologies. I’m a much different person now and I know you all are too… I’m darn near 30 now and still think about you guys often

Not making confessions anymore, but if anyone wishes to reach out to this person then their inbox is open.

Thank you Kes for reaching out.

[sapientsapiens]

Just wrapped up the assignments on the final chapter of the #mlzoomcamp on model deployment in Kubernetes clusters. Got foundational hands-on experience with Tensorflow Serving, gRPC, Protobuf data format, docker compose, kubectl, kind and actual Kubernetes clusters on EKS.

[newcodesociety]

[bytesizego]

🚀 Getting Started with Golang: A Developer's Journey 🛠️

Golang is a game-changer for developers seeking efficiency and simplicity. Whether you’re building web servers 🌐 or mastering concurrency 🧵, Go’s clean syntax and robust performance make it ideal for high-performance apps.

In this blog, I’ll share byte-sized tips 💡, tutorials, and insights to help you level up your Go skills. For more in-depth resources and courses, check out ByteSizeGo. Let’s dive into debugging, gRPC, and everything Go! 🎯

Stay tuned! 🔥

[robomad]

A Comprehensive Guide to Building Microservices with Node.js

Introduction:The microservices architecture has become a popular approach for developing scalable and maintainable applications. Unlike monolithic architectures, where all components are tightly coupled, microservices allow you to break down an application into smaller, independent services that can be developed, deployed, and scaled independently. Node.js, with its asynchronous, event-driven…

[augustheart]

more people should know about bird banding abbreviation codes because they make talking about certain species so much easier. they're four-letter codes that correspond to a bird's common name.*

for most bird names, they take the first two letters of the first part of the name and the first two letters of the last part and combine them. so GREG is GReat EGret, SPTO is SPotted TOwhee, LEGO is LEsser GOldfinch, etc. for birds with more than two parts to their names, the letters are taken from all of the parts. so NSWO is Northern Saw-Whet Owl, GHOW is Great Horned OWl, GRPC is GReater Prairie-Chicken, etc.

of course, some birds only have one part to their name. so for those birds the first four letters become the code. CANV is CANVasback, WILL is WILLet, GYRF is GYRFalcon.

but there are birds that would normally overlap, like AMerican GOshawk and AMerican GOldfinch, or CAnada GOose and CAckling GOose. so their codes need to be rearranged and break the typical convention--now AGOL is American GOLdfinch and AGOS is American GOShawk, and CANG is CANada Goose and CACG is CACkling Goose. these ones are less intuitive but usually still easy to figure out.

so now you know you can say NOPO when you see a northern pygmy-owl, SNEG when you see a snowy egret, BRBL when you see a brewer's blackbird, or AMCR when you see an american crow! good luck figuring out how to pronounce some of those.

(*things get more complicated when you start using the six-letter codes for the latin names... like ABTO/abert's towhee, which is Melozone aberti/MELABE. although it's definitely less time-consuming when you can say PHEFAS for Pheugopedius fasciatoventris, the black-bellied wren (BBEW). we'll do that some other day.)

[ashfordvalleyhq]

Hey there! I haven’t been in the grpc in YEARS but I’ve been really missing it lately; this looks so much like it used to back in the day and I’m really excited! Anyway, I’m thinking about Dave Karofsky, but I’m not sure which direction I’d go with him. Just curious if you have any FC’s in mind (or if his og fc, Max Adler, is still a viable option? Again, been so long since I’ve been a part of the community, I’m unsure!) I was also wondering how closely I should stick to his original canon storyline and how much I can headcanon or change slightly.

Hey there, thank you so much! Max Adler is definitely good to use, though if you'd like some alternate options for a FC, here's a list of some we think would work great as well: Oliver Stark, Brant Daugherty, Taron Egerton, Aaron Taylor-Johnson, Cody Christian, Derek Theler.

As for his character, the setting itself is very much "alternate universe" so specifics with storylines don't have to be a part of the character if you don't want to. It's more about keeping the canon vibe of the character, plus as the show was (for the most part) depicting them in high school and they're all adults in this verse, there's room to have growth within that character vibe as well. Hope this helps and we hope to see an app from you!

[handyouthemoon]

"Every Day is a Good Day to Eat Cake" (2022) is both homáge to Crazy Horse's "It's a good day to die" (context: he was speaking of fighting for the survival of his people against violent settling & colonizing) & my undying belief that cake is a joy, a pleasure, that everyone deserves. I have been known to say that cake makes everything better. Anyone who wants cake should let themself shamelessly have cake. This world is a dumpster fire, as we all know, so take your (unharmful to others) joy where you can.

9x12 inches; acrylic, paper, & gel pen on canvas board.

Due to age, I'm reducing this to $25. $8 to ship, which is in the U.S. only & via USPS Priority with tracking & insurance. Local West Michigan folks can arrange pick-up, free, at my home or GRPC. MESSAGE to arrange purchase, please.

***

No, I don't take commissions. If you like my work, please choose from the 100+ pieces I have available.

No, I don't deal with NFTs

[fionaroleplays]

since you're bringing the theme blog back or trying to revive it, any chance you'd consider reviving gleerpconfessions? i know the grpc is still just barely alive but could be a great place for memories to be shared and every blog that's been started since that one died out has only just died out itself or been abandoned or deleted.

If people are willing to send confessions about positive things in about the Glee RPC past or present rather than 10 vents a day, then i'd consider it. Though i'm rusty at graphic making right now as the software I was using died after my computer did a windows update. So i'm experimenting with Photopea with mixed results.

[govindhtech]

CloudFront Now Supports gRPC Calls For Your Applications

Your applications’ gRPC calls are now accepted by Amazon CloudFront.

You may now set up global content delivery network (CDN), Amazon CloudFront, in front of your gRPC API endpoints.

An Overview of gRPC

You may construct distributed apps and services more easily with gRPC since a client program can call a method on a server application on a separate machine as if it were a local object. The foundation of gRPC, like that of many RPC systems, is the concept of establishing a service, including the methods that may be called remotely along with their parameters and return types. This interface is implemented by the server, which also uses a gRPC server to manage client requests. The same methods as the server are provided by the client’s stub, which is sometimes referred to as just a client.

Any of the supported languages can be used to write gRPC clients and servers, which can operate and communicate with one another in a range of settings, including your desktop computer and servers within Google. For instance, a gRPC server in Java with clients in Go, Python, or Ruby can be readily created. Furthermore, the most recent Google APIs will include gRPC interfaces, making it simple to incorporate Google functionality into your apps.

Using Protocol Buffers

Although it can be used with other data formats like JSON, gRPC by default serializes structured data using Protocol Buffers, Google’s well-established open source method.

Establishing the structure for the data you wish to serialize in a proto file a regular text file with a.proto extension is the first step in dealing with protocol buffers. Protocol buffer data is organized as messages, each of which is a brief logical record of data made up of a number of fields, or name-value pairs.

After defining your data structures, you can use the protocol buffer compiler protoc to create data access classes from your proto specification in the language or languages of your choice. These offer methods to serialize and parse the entire structure to and from raw bytes, along with basic accessors for each field, such as name() and set_name(). For example, executing the compiler on the aforementioned example will produce a class named Person if you have selected C++ as your language. This class can then be used to serialize, retrieve, and populate Person protocol buffer messages in your application.

You specify RPC method parameters and return types as protocol buffer messages when defining gRPC services in standard proto files:

Protoc is used by gRPC with a specific gRPC plugin to generate code from your proto file. This includes the standard protocol buffer code for populating, serializing, and retrieving your message types, as well as generated gRPC client and server code.

Versions of protocol buffers

Although open source users have had access to protocol buffers for a while, the majority of the examples on this website use protocol buffers version 3 (proto3), which supports more languages, has a little simplified syntax, and several helpful new capabilities. In addition to a Go language generator from the golang/protobuf official package, Proto3 is presently available in Java, C++, Dart, Python, Objective-C, C#, a lite-runtime (Android Java), Ruby, and JavaScript from the protocol buffers GitHub repository. Additional languages are being developed.

Although proto2 (the current default protocol buffers version) can be used, it advises using proto3 with gRPC instead because it allows you to use all of the languages that gRPC supports and prevents incompatibilities between proto2 clients and proto3 servers.

What is gRPC?

A contemporary, open-source, high-performance Remote Procedure Call (RPC) framework that works in any setting is called gRPC. By supporting pluggable load balancing, tracing, health checking, and authentication, it may effectively connect services both within and between data centers. It can also be used to link devices, browsers, and mobile apps to backend services in the last mile of distributed computing.

A basic definition of a service

Describe your service using Protocol Buffers, a robust language and toolkit for binary serialization.

Launch swiftly and grow

Use the framework to grow to millions of RPCs per second and install the runtime and development environments with only one line.

Works on a variety of platforms and languages

For your service, automatically create idiomatic client and server stubs in several languages and platforms.

Both-way streaming and integrated authentication

Fully integrated pluggable authentication and bi-directional streaming with HTTP/2-based transport

For creating APIs, gRPC is a cutting-edge, effective, and language-neutral framework. Platform-independent service and message type design is made possible by its interface defining language (IDL), Protocol Buffers (protobuf). With gRPC, remote procedure calls (RPCs) over HTTP/2 are lightweight and highly performant, facilitating communication between services. Microservices designs benefit greatly from this since it facilitates effective and low-latency communication between services.

Features like flow control, bidirectional streaming, and automatic code generation for multiple programming languages are all provided by gRPC. When you need real-time data streaming, effective communication, and great performance, this is a good fit. gRPC may be an excellent option if your application must manage a lot of data or the client and server must communicate with low latency. However, compared to REST, it could be harder to master. Developers must specify their data structures and service methods in.proto files since gRPC uses the protobuf serialization standard.

When you put CloudFront in front of your gRPC API endpoints, we see two advantages.

Initially, it permits the decrease of latency between your API implementation and the client application. A global network of more than 600 edge locations is provided by CloudFront, with intelligent routing to the nearest edge. TLS termination and optional caching for your static content are offered by edge locations. Client application requests are sent to your gRPC origin by CloudFront via the fully managed, high-bandwidth, low-latency private AWS network.

Second, your apps gain from extra security services that are set up on edge locations, like traffic encryption, AWS Web Application Firewall’s HTTP header validation, and AWS Shield Standard defense against distributed denial of service (DDoS) assaults.

Cost and Accessibility

All of the more than 600 CloudFront edge locations offer gRPC origins at no extra cost. There are the standard requests and data transfer costs.

Read more on govindhtech.com

[csharp-space]

Boost Data Efficiency: Fetching from Database with gRPC Protobuf in ASP....

[hindintech]

You can learn NodeJS easily, Here's all you need:

1.Introduction to Node.js

• JavaScript Runtime for Server-Side Development

• Non-Blocking I/0

2.Setting Up Node.js

• Installing Node.js and NPM

• Package.json Configuration

• Node Version Manager (NVM)

3.Node.js Modules

• CommonJS Modules (require, module.exports)

• ES6 Modules (import, export)

• Built-in Modules (e.g., fs, http, events)

4.Core Concepts

• Event Loop

• Callbacks and Asynchronous Programming

• Streams and Buffers

5.Core Modules

• fs (File Svstem)

• http and https (HTTP Modules)

• events (Event Emitter)

• util (Utilities)

• os (Operating System)

• path (Path Module)

6.NPM (Node Package Manager)

• Installing Packages

• Creating and Managing package.json

• Semantic Versioning

• NPM Scripts

7.Asynchronous Programming in Node.js

• Callbacks

• Promises

• Async/Await

• Error-First Callbacks

8.Express.js Framework

• Routing

• Middleware

• Templating Engines (Pug, EJS)

• RESTful APIs

• Error Handling Middleware

9.Working with Databases

• Connecting to Databases (MongoDB, MySQL)

• Mongoose (for MongoDB)

• Sequelize (for MySQL)

• Database Migrations and Seeders

10.Authentication and Authorization

• JSON Web Tokens (JWT)

• Passport.js Middleware

• OAuth and OAuth2

11.Security

• Helmet.js (Security Middleware)

• Input Validation and Sanitization

• Secure Headers

• Cross-Origin Resource Sharing (CORS)

12.Testing and Debugging

• Unit Testing (Mocha, Chai)

• Debugging Tools (Node Inspector)

• Load Testing (Artillery, Apache Bench)

13.API Documentation

• Swagger

• API Blueprint

• Postman Documentation

14.Real-Time Applications

• WebSockets (Socket.io)

• Server-Sent Events (SSE)

• WebRTC for Video Calls

15.Performance Optimization

• Caching Strategies (in-memory, Redis)

• Load Balancing (Nginx, HAProxy)

• Profiling and Optimization Tools (Node Clinic, New Relic)

16.Deployment and Hosting

• Deploying Node.js Apps (PM2, Forever)

• Hosting Platforms (AWS, Heroku, DigitalOcean)

• Continuous Integration and Deployment-(Jenkins, Travis CI)

17.RESTful API Design

• Best Practices

• API Versioning

• HATEOAS (Hypermedia as the Engine-of Application State)

18.Middleware and Custom Modules

• Creating Custom Middleware

• Organizing Code into Modules

• Publish and Use Private NPM Packages

19.Logging

• Winston Logger

• Morgan Middleware

• Log Rotation Strategies

20.Streaming and Buffers

• Readable and Writable Streams

• Buffers

• Transform Streams

21.Error Handling and Monitoring

• Sentry and Error Tracking

• Health Checks and Monitoring Endpoints

22.Microservices Architecture

• Principles of Microservices

• Communication Patterns (REST, gRPC)

• Service Discovery and Load Balancing in Microservices