Tech stack for APIs

1 votes

Define a standard tech stack for APIs, so API producers don't have to figure it out for themselves.

Not planned make-building-apis-easier platform platform-phase-2 Suggested by: Tony Heap (11 Jul, '20) • Upvoted: 11 Jul, '20 • Comments: 2

Comments: 2

02 Sep, '20
Tony Heap Admin
After further discussion we have decided that this is not something for the API Management team to deliver at this point in time - there isn't currently a clear need for a standard tech stack, and if there were we would probably look to hook into wider platform guidance rather than API-specific guidance.
22 Jan, '21
Grahame Horner
IMHO any API that defines the tech stack for producers; is NOT a good API. We will in a world where technology rapidly changes and APIs designs should support standards in protocols (REST json/xml, gRPC, SOAP) and NOT make tech used to implement (Java, go, php, .NET C#) said protocols. Typically developer teams are ployglot and therefor they can use any tooling stack of choice as their first class citizen.