We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Implementing a STAC Service with gRPC and Protocol Buffers

Formal Metadata

Title
Implementing a STAC Service with gRPC and Protocol Buffers
Alternative Title
How to host and access STAC Imagery using Google's gRPC Remote Procedure Call framework and Protobuf messages
Title of Series
Number of Parts
295
Author
Contributors
License
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
At Swiftera we've built a Spatio Temporal Asset Catalog (STAC) service using the gRPC framework and protobuf messages (instead of the OpenAPI framework and JSON messages) . The Remote Procedure Call framework, gRPC, and the protobuf message format are what Google uses internally for it's micro-services (10s of billions of messages a second). Since Google open sourced gRPC 4 years ago, it has been widely adopted by companies moving massive amounts of data (Netflix, Salesforce, Spotify and others). But it isn't only about performance, it's also an suprisingly easy framework to get up and running. At FOSS4GNA we open sourced our NAIP metadata service and the IDL defining the services and messages. By Bucharest we plan to have added Landsat and Sentinel to our public gRPC service. We want to share more about what it's like to work with gRPC and the ease of development for hosting your own gRPC services.
Keywords