Define a standard tech stack for APIs, so API producers don't have to figure it out for themselves.
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.
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.
0 / 1,000
* Your name will be publicly visible
* Your email will be visible only to moderators
This feedback board is powered by Feature Upvote.
When submitting your email with a suggestion or comment, Feature Upvote uses your email to
Your email is never displayed to other users. NHS Digital API Management staff will be able to see your email address.
Feature Upvote's Acceptable Use Policy can be summarized as:
Read the full Acceptable Use Policy (in English)
We’ll email you when the status of the suggestion changes. You can unsubscribe at any time with a single click.
* Comments and upvotes from this suggestion will be moved to another suggestion.
Edit the selected suggestion and create a new one.
Comments and upvotes will also be moved.