Blog posts: drop invalid & unnecessary Hugo aliases (#649)

This commit is contained in:
Patrice Chalin 2021-02-15 15:30:46 -05:00 committed by GitHub
parent dfc8082670
commit a1b660a033
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 4 additions and 7 deletions

View File

@ -3,7 +3,6 @@ title: gRPC releases Beta, opening door for use in production environments
date: 2015-10-26
author:
name: Mugur Marculescu
aliases: ["blog/beta_release"]
---
The gRPC team is excited to announce the immediate availability of gRPC Beta. This release marks an important point in API stability and going forward most API changes are expected to be additive in nature. This milestone opens the door for gRPC use in production environments.

View File

@ -7,7 +7,6 @@ author:
link: https://cloud.google.com
blurb: Originally written by Varun Talwar with additional content by Kailash Sethuraman and others at Google.
thumbnail: ../img/gcp-icon.png?raw=true
aliases: ["blog/gablogpost"]
---
Today, the gRPC project has reached a significant milestone with its [1.0 release](https://github.com/grpc/grpc/releases).

View File

@ -7,7 +7,6 @@ author:
guest: true
blurb: Originally written by Dale Hopkins with additional content by Lisa Carey and others at Google
thumbnail: /img/vend-icon.png?raw=true
aliases: ["blog/vendastagrpc"]
---

View File

@ -9,10 +9,9 @@ authors:
blurb: |
Thanks to the VSCO engineers that worked on this migration: Steven Tang, Sam Bobra, Daniel Song, Lucas Kacher, and many others.
thumbnail: ../img/vsco-logo.png?raw=true
aliases: ["blog/vscogrpc"]
---
Our guest post today comes from Robert Sayre and Melinda Lu of VSCO.
Our guest post today comes from Robert Sayre and Melinda Lu of VSCO.
Founded in 2011, [VSCO](https://vsco.co) is a community for expression—empowering people to create, discover and connect through images and words. VSCO is in the process of migrating their stack to gRPC.
@ -30,12 +29,12 @@ As a first step in bringing gRPC to our mobile clients, weve shipped telemetr
One slight roadblock we ran into was the need for our clients to maintain compatibility with our JSON implementation as we ramp up, and for integration with vendor SDKs. This required a little bit of key-value coding on iOS, but it got more difficult on Android. We ended up having to write a protobuf compiler plugin to get the reflection features we needed while maintaining adequate performance. Drawing from that experience, weve made a concise [example protoc plugin](https://github.com/vsco/protoc-demo) built with [Bazel](https://bazel.io/) available on GitHub.
As more and more of our data becomes available in protocol buffer form, we plan to build upon this unified schema to expand our machine-learning and analytics systems. For example, we write our Kafka database replication streams to Amazon S3 as [Apache Parquet](https://parquet.apache.org/), an efficient columnar disk-storage format. Parquet has low-level support for protocol buffers, so we can use our existing data definitions to write optimized tables and do partial deserializations where desired.
As more and more of our data becomes available in protocol buffer form, we plan to build upon this unified schema to expand our machine-learning and analytics systems. For example, we write our Kafka database replication streams to Amazon S3 as [Apache Parquet](https://parquet.apache.org/), an efficient columnar disk-storage format. Parquet has low-level support for protocol buffers, so we can use our existing data definitions to write optimized tables and do partial deserializations where desired.
From S3, we run computations on our data using Apache Spark, which can use our protocol buffer definitions to define types. Were also building new machine-learning applications with [TensorFlow](https://www.tensorflow.org/). It uses protocol buffers natively and allows us to serve our models as gRPC services with [TensorFlow Serving](https://tensorflow.github.io/serving/).
So far, weve had good luck with gRPC and Protocol Buffers. They dont eliminate every integration headache. However its easy to see how they help our engineers avoid writing a lot of boilerplate RPC code, while side-stepping the endless data-quality papercuts that come with looser serialization formats.

View File

@ -100,6 +100,7 @@
/2018/01/22/grpc-go-engineering-practices* /blog/grpc-go-engineering-practices
/blog/2017-08-22-grpc-go-perf-improvements* /blog/grpc-go-perf-improvements
/blog/a_short_introduction_to_channelz* /blog/a-short-introduction-to-channelz
/blog/beta_release* /blog/beta-release
/blog/bazel_rules_protobuf* /blog/bazel-rules-protobuf
/blog/flatbuffers /blog/grpc-flatbuffers
/blog/gablogpost* /blog/ga-announcement