CaperAi/pronto
View on GitHub ↗ ★ 6 Java
Protobuf ORM
8 mentions on Hacker News by 1 person: 1 story, 7 comments · first 2020-08-21 · latest 2021-12-09
20082026
-
…you the voltages from the physical layer, it is decoded). Buff is building that tooling. [0] - https://github.com/CaperAi/pronto
comment by gravypod · 2021-12-09 · in Buf raises $93M to deprecate REST/JSON -
…written translation layers for such systems and it's not too bad. See this project from $job - 1: https://github.com/CaperAi/pronto It allowed us to have a single model for storage in the DB, for sending between services, and syncing to…
comment by gravypod · 2021-10-23 · in Parsing gigabytes of JSON per second -
…conventions for a proto and make amazing libraries for your team. At a previous job I made this: https://github.com/CaperAi/pronto/ Made it super easy to prototype multiple services as if you mock a service backed by memory we could plop…
comment by gravypod · 2021-09-23 · in gRPC for Microservices Communication -
…something similar to this except the opposite direction at a previous job. It was called Pronto: https://github.com/CaperAi/pronto/ It allowed us to store and query Protos into MongoDB. It wasn't perfect (lots of issues) but the idea was…
comment by gravypod · 2021-09-09 · in How We Went All In on sqlc/pgx for Postgres and Go -
…treasurer). It's not the best tool by any means. It's just the most free (price and libre). [0] - https://github.com/CaperAi/pronto/ [1] - https://github.com/CaperAi/bazel_compose [2] - https://github.com/CaperAi/branchpoke [3] -…
comment by gravypod · 2021-05-16 · in Ask HN: What are some tools / libraries you built yourself? -
…job: 1. https://github.com/CaperAi/branchpoke 2. https://github.com/CaperAi/bazel_compose 3. https://github.com/CaperAi/pronto These were the ones that were easy to pluck from my job's monorepo and generally applicable. As someone who is…
comment by gravypod · 2020-12-14 · in Ask HN: Was 20% time a good policy for Google's working culture? -
…configuration options for all services/devices 2. Define data models 3. Persist them into our DB: https://github.com/CaperAi/pronto 4. Define our APIs It's extremely convenient to have a single source of truth.
comment by gravypod · 2020-11-14 · in API design is stuck in the past