I would point out that the term "API" refers to any (semi-)public facing interface. Accessible methods to the includer in an includable package are also an API.
This article is talking strictly about APIs exposed on an application-level, i.e. Service-to-Service.
I totally agreee with you. But if I would have tried to explain every concet it will be very difficult fopr beginner to understand. And I tried to put other concepts in simple words but couldn't.
I also got confused with this. I believed at a certain point of my career that APIs are only what is described in this article. I would elaborate further that APIs are also Libraries and Frameworks (examples: blog.ndepend.com/top-10-net-5-0-ne..., docs.microsoft.com/en-us/dotnet/api/, ..) and that the article is focusing only on Remote/Web APIs? I would also mention gRPC and GraphQL which are emerging and becoming significant at the time of writing this comment.
I would point out that the term "API" refers to any (semi-)public facing interface. Accessible methods to the includer in an includable package are also an API.
This article is talking strictly about APIs exposed on an application-level, i.e. Service-to-Service.
I totally agreee with you. But if I would have tried to explain every concet it will be very difficult fopr beginner to understand. And I tried to put other concepts in simple words but couldn't.
I also got confused with this. I believed at a certain point of my career that APIs are only what is described in this article. I would elaborate further that APIs are also Libraries and Frameworks (examples: blog.ndepend.com/top-10-net-5-0-ne..., docs.microsoft.com/en-us/dotnet/api/, ..) and that the article is focusing only on Remote/Web APIs? I would also mention gRPC and GraphQL which are emerging and becoming significant at the time of writing this comment.
Thank you for your suggestion. I wanted to add those topics. But, I wanted to write something focused for beginners that's the reason I didn't add it.