dsinghvi

4 ms·

1.
by dsinghvi 3y ago
Disclosure: I'm a contributor to Fern. This is good feedback that we need to provide more examples starting with OpenAPI instead of with the Fern Definition. For some context, we convert the OpenAPI spec into a Fern definition and then
2.
by dsinghvi 3y ago
:wave: Hey Mark -- I'm one of the primary contributors to Fern. +1 to your comment about how needing to support multiple languages results in not being able to leverage certain language specific features. We've tried the best to m
3.
by dsinghvi 3y ago
@sthuck I'm working on an alternative in this space called Fern. Like gRPC, you define your schema and use it to generate client libraries + server code. Fern integrates with FastAPI/Express/Spring and generates clients in Py
4.
Show HN: Stop writing untyped express routes(loom.com)
1 points by dsinghvi 4y ago|0 comments
5.
Schema-first API development with FastAPI(github.com)
3 points by dsinghvi 4y ago|0 comments
6.
by dsinghvi 4y ago
https://www.personal.ai/
7.
by dsinghvi 4y ago
Got it -- looks like AWS API Gateway also does this out of the box.
8.
by dsinghvi 4y ago
Got it! Based on your comment / some googling it sounds like the common use case is for managing internal secrets. Do you think it's a good fit if you want to use it for managing API Keys for your public API (you want your custome
9.
by dsinghvi 4y ago
It seems like in-house is the way to go since there are no other alternatives. Things we would have to build: - Generating API Keys (with expiry) - Storing API Keys securely - Revoking API Keys - Adding metadata to API Keys
10.
by dsinghvi 4y ago
I'm not so much talking about the type of token issued (JWT/Opaque), but more about the service that manages issuing and revoking keys. (i.e. something similar to what Stripe has on their developer portal https://stripe
11.
Ask HN: What do you use for API Key Management?
7 points by dsinghvi 4y ago|11 comments