--
You received this message because you are subscribed to the Google Groups "API Craft" group.
To unsubscribe from this group and stop receiving emails from it, send an email to api-craft+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/api-craft/c7a1e0a0-53e2-481a-a941-988c23ff88ed%40googlegroups.com.
+27 21 680 5252 | bbli...@equalexperts.com
[=] EQUAL EXPERTS Making Software. Better.
Hi Miguel,I unfortunately don't have a percentage for you, but I have definitely got first hand experience of this happening more than once. I think as soon as people know something is available, they want to use it, and why not! My approach to building API's is to assume it's going to be public, and design accordingly. This assumes that you have the time to do so, and have weighed up the cost/benefit of not designing it for external use.I think if the decision is taken, for whatever reason, to not design as if it will be consumed externally, everyone is aware that if this situation does arise a rewrite will be required.RegardsBrian
On Wed, 22 Jan 2020 at 06:12, miqui <migm...@gmail.com> wrote:
Hi, community,--So, I was wondering what percentage of APIs that are deemed "only for our application/platform/team tools" (private API?) do you think eventually becomes (promoted to?) a public API? or a partner API?I typically get the usual private APIs "pushback" that these types of APIs should not follow the same design guidelines as public or partner API. Thoughts?rgdsMiguel
You received this message because you are subscribed to the Google Groups "API Craft" group.
To unsubscribe from this group and stop receiving emails from it, send an email to api-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/api-craft/c7a1e0a0-53e2-481a-a941-988c23ff88ed%40googlegroups.com.