Web Dev full-stack [LAMP] since 2005, but much heavier on the JS stuff these days.
Jack of all Stacks, Master of some.
Always looking to learn new things. Always glad to help out, just ask.
Location
Atlanta, GA
Education
B.S. in Biochemistry 2004, M.S. in Computer Information Systems 2007
All of this is a very nice long write up about APIs and various ways these are implemented.
I would like to state though that an API is really just this:
the client [a computer, any device that will send a request]
an endpoint [any url that accepts requests and processes them and returns them]
What the client is [pc,laptop,mobile, another server] doesn't matter.
What the endpoint is [server file, custom subdomain, root domain, lambda function] doesn't matter.
As long as the information requested is received by the client.
We've called these SOAP requests, endpoints, APIs, Rest APIs, Json endpoints, XML endpoints, etc etc etc.
In the end, it's a request and a response, that's it.
KISS method applies and helps newbies understand it faster.
B.Eng in MECH. ENG || 4X YEARS as a SOFTWARE ENG. Work with => | Python | fastAPI | Flask | Django | JavaScript | PHP | Laravel | PostgreSQL | MYSQL | Dart * Flutter
All of this is a very nice long write up about APIs and various ways these are implemented.
I would like to state though that an API is really just this:
What the client is [pc,laptop,mobile, another server] doesn't matter.
What the endpoint is [server file, custom subdomain, root domain, lambda function] doesn't matter.
As long as the information requested is received by the client.
We've called these SOAP requests, endpoints, APIs, Rest APIs, Json endpoints, XML endpoints, etc etc etc.
In the end, it's a request and a response, that's it.
KISS method applies and helps newbies understand it faster.
You correct as well... 💪💪💪