Amazon VPC PrivateLink VS Protobuf

AWS VPC Interface Endpoints are a component of AWS's PrivateLink infrastructure. AWS PrivateLink provides private connectivity between virtual private clouds (VPCs), supported AWS services, and your on-premises networks without exposing your traffic to the public internet. - Source: dev.to / about 1 year ago

On AWS the most secure way to do this is to deploy your service to a private VPC then use AWS Private Link to connect them https://aws.amazon.com/privatelink/. Source: over 1 year ago

AWS PrivateLink service has been around for a while, and it allows you to publish services from one VPC that you can access from another VPC. Through VPC Endpoint (VPCE), you can extend services behind an NLB (Network Load Balancer) into a different VPC. PrivateLink is made up of NLB and VPCE in a form of Elastic Network Interfaces. Few things to note, Private Link is uni-directional and only works with TCP traffic. - Source: dev.to / almost 2 years ago

- AWS SaaS Factory program with whitepapers etc. https://aws.amazon.com/partners/programs/saas-factory/ - Just recently a webinar series about SaaS: https://buildingsaasonaws.splashthat.com/ - Technical mechanism in AWS PrivateLink how you can sell your SaaS service to AWS Customers without traversing over the Internet: https://aws.amazon.com/privatelink/ - AWS Marketplace for SaaS products where you can start... Source: over 2 years ago

Elastic Load Balancing now supports forwarding traffic directly from Network Load Balancer (NLB) to Application Load Balancer (ALB). With this feature, you can now use AWS PrivateLink and expose static IP addresses for applications built on ALB. Source: over 2 years ago

Protocol Buffers: https://developers.google.com/protocol-buffers. - Source: dev.to / about 1 year ago

ProtocolBuffers’ OneOf message addresses the case of having a message with many fields where at most one field will be set at the same time. - Source: dev.to / over 1 year ago

That's definitely the bigger thing. I think something like Protocol Buffers (Protobuf) is what you're looking for there. Output the data and consume it by something that can handle the analysis. Source: over 1 year ago

These protocols prevent an O(N x M) explosion of code that have to solve for many cases. For example, since JSON is an almost ubiquitous format for wire transfer (although other things do exist like protobufs), if I had N data formats that I want to serialize, I only need to write N serializers/deserializers (SerDes). If there was no such narrow waist and there were M alternatives to JSON in wide usage, I would... Source: over 1 year ago

gRPC uses protocol buffers (it is an open source message format) as the default method of communication between client and server. Also, gRPC uses HTTP/ 2 as the default protocol. - Source: dev.to / over 1 year ago