Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
norman70688470778dI'm not aware of any naming standards in such case, but staging.api.example.com tells me, that there will be (production) api.example.com at some point while api.staging.example.com suggest some sort of staging environment where api is being, well, staged.
Typically I work with APIs that are:
This gives a clear and precise understanding of which environment you are about to hit/send data too.
as for naming conventions, I doubt there's any written law for subdomians being used as routing, even @heyheni's two links don't include anything outside of just api.example.com 🤷♂️
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job