Tom CardenJan 8, 2023

Thoughtful tech friends, if you were building a developer-facing API from scratch today what tech and SaaS would you use to get to market quickly with a quality product?

And: what features and considerations are “table stakes” for you to consider using someone else’s API?

#tech #apis #saas

Show threadJonathan BeriJan 8, 2023
@randometc big question that's missing is who is the consumer? Internal vs external, free or paid service, what kind of client (servers, mobile, web,) are there existing standards to conform to?
Show threadTom CardenJan 8, 2023
@jberi interested to hear why all that makes a difference though!
Show threadJonathan Beri

@randometc not enough space to go through all the details, unfortunately. But two things those touch on are:

* Are there technical constraints you must align with
* Are there expectations of your consumers

Just some examples of what to consider - Internal APIs either have existing infra and/or people to operate something like Kong. External API need user sign up while internal apps probably HAVE TO use corporate SSO. Web apps are probably all client-side JS, so gRPC is very hard to consume.

Jan 8, 2023 at 10:13pmWeb
Show threadJonathan BeriJan 8, 2023
@randometc I personally haven't used Zuplo but I've gotten the demo and unless you have additional constraints, I'd say start there. Build the API you want with the language/framework you're most proficient in and offload the infra. You can always bring it in house.