googleapis
thin-backend
googleapis | thin-backend | |
---|---|---|
13 | 43 | |
6,522 | 1,227 | |
1.0% | 0.0% | |
9.6 | 0.0 | |
4 days ago | over 1 year ago | |
Starlark | JavaScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
googleapis
-
REST vs gRPC
Rich Error Model: This model enables servers to return and clients to consume additional error details expressed as one or more protobuf messages. It further specifies a standard set of error message types to cover the most common error (QuotaFailure, PreconditionFailure, BadRequest, etc). When an error occurs, the server returns the appropriate status code along with an optional error message.
-
Mullvad Leta
They list search in their public api
https://github.com/googleapis/googleapis/blob/288aa7fb71c9b6...
-
Reasons to use gRPC/Protobuf?
We structure the repo according to proto packages. It's quite similar to how the googleapis repository is structured.
-
Problem Details for HTTP APIs
It's unfortunate that the spec doesn't contain custom fields to a sub-object like other RPC specs, like proto Status [1]. They should have had the message go into a field named "message" and not "detail". And have a field like "details" where the opaque type is serialized, which should be named by the "type" field. The problem is that systems with existing error types may have field name conflicts with type, title, status, detail, or instance, so we'd just dump the actual error into a custom "extension member" which by definition, isn't standard.
[1] https://github.com/googleapis/googleapis/blob/1c8a25ab153eef...
-
[Media] Dear Google, When Rust? Sincerely, Internet
Protobuf (https://github.com/googleapis/googleapis)
-
gRPC vs REST: Comparing API Styles in Practice
All the required changes can be viewed in our last demo, the grpc-rest-app implementation. First, we need to update our proto service interface to help the proxy service make our gRPC service methods available at the right URLs and for the correct HTTP operations. To do this, the Google API HTTP library provides annotations we can add to our proto to describe the correct mappings. The buf tool allows us to include the googleapis dependency as a plugin in our buf.yaml file).
-
Code Design Decision – Always throw custom exceptions
I think this only makes sense if the 3rd party is also throwing custom exceptions.
If you want to reduce coupling you should avoid throwing custom exceptions at all. Semantic information can go in the error message and log. The error type should be used to indicate to your program whether an error is recoverable, retriable or some other action needs to be taken. For example google on has 16 canonical error codes for all APIs.
https://github.com/googleapis/googleapis/blob/master/google/...
-
Microservice Communication
OpenAPI and possibly developing reusable, versioned client libraries could help, but it's a major undertaking that gRPC makes redundant. I'd be tempted to use grpc-gateway even if I had to implement a REST API. Try looking into buf and monorepo structures for proto management, e.g. something like GoogleCloudPlatform/microservices-demo. For more thorough proto and grpc-gateway definition examples, see googleapis/googleapis.
-
Convex vs. Firebase
Firestone does provide global consistency, so the following quote is incorrect:
> In Cloud Firestore, the data on the client are loaded from the database at different points in time. Even if you listen for realtime updates, results from separate queries will not remain in sync. This creates consistency anomalies and bugs in your app.
Here is a link to the protocol documentation that the clients use to support it: https://github.com/googleapis/googleapis/blob/d0b394f188e8c3...
I'd link to the client implementation but it's quite involved.
-
Useful Old Technologies: ASN.1 (2013)
Well there is Timestamp defined as a well known type which is available to all implementations despite not being a primitive type [1]. Plus one is obviously able to define any other custom types if necessary- eg as seen in [2].
[1] https://developers.google.com/protocol-buffers/docs/referenc...
[2] https://github.com/googleapis/googleapis/blob/master/google/...
thin-backend
-
Ask HN: How would you refactor a big project in 2023?
A tool like https://thin.dev/ might be good for you. You can port and serve functionality a little bit at a time into thin and use their managed postgres db and the schema editor to handle the new fields in the backend.
-
Why We're Moving on from Firebase
Check out thin.dev https://thin.dev/ It uses SQL DDL statements literally as the building blocks for everything.
-
Prisma vs. Thin Backend
Postgres database has been gaining more popularity because of its advanced database and scalability. Created by digitally induced, Thin Backend is simplifying Postgres by giving users a backend server that has an API that connects with Postgres DB. You can integrate Thin Backend with:
- Thin Backend - Instant Postgres Backend for React/Vue/Svelte/... Apps with Realtime, Optimistic Updates & Auto-generated TypeScript Bindings
- Thin Backend
-
Best React Developer Experience?
React for UI TypeScript for Type Safety thin.dev for Data + State management
-
Show HN: PocketBase – open-source realtime back end in 1 file
Check out https://thin.dev/ :) It's similar, supports self-hosting and uses postgres. Quick demo video here: https://www.youtube.com/watch?v=-jj19fpkd2c&t=3s
(I'm founder of Thin)
-
10 Years of Meteor: My experience with a pioneering JavaScript framework
Real-time by default for everything is really a fun way to write web apps. A little bit inspired by Meteor we've build Thin Backend, which provides a real-time API for querying data and writing to a postgres database. If you're interested, check it out at https://thin.dev/ or check the demo video https://www.youtube.com/watch?v=-jj19fpkd2c
-
An Alternative Approach to State Management with Redux
If you're curious, give it a try at thin.dev.
What are some alternatives?
supabase - The open source Firebase alternative.
pocketbase - Open Source realtime backend in 1 file
powerproto - 🎉 An awesome version control tool for protoc and its related plugins.
postgrest - REST API for any Postgres database
readyset - Readyset is a MySQL and Postgres wire-compatible caching layer that sits in front of existing databases to speed up queries and horizontally scale read throughput. Under the hood, ReadySet caches the results of cached select statements and incrementally updates these results over time as the underlying data changes.
pg_graphql - GraphQL support for PostgreSQL
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
gogoprotobuf - [Deprecated] Protocol Buffers for Go with Gadgets
ihp - 🔥 The fastest way to build type safe web apps. IHP is a new batteries-included web framework optimized for longterm productivity and programmer happiness
parthenon - The Symfony SaaS boilerplate
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production