Skip to main content
added 181 characters in body
Source Link
JacquesB
  • 61k
  • 21
  • 133
  • 187
  1. Yes, what you describe is an API. Any software interface which is designed to be called by software clients is an API. Your architecture sound like RPC (remote procedure calls) over HTTP, which is a common form of API.

  2. Probably not. REST is not designed for API's. REST is an architectural style optimized for large-scale distributed hypermedia. It is not designed for API's like yours, where a single frontend communicate with a single backend.

  1. Yes, what you describe is an API. Any software interface which is designed to be called by software clients is an API. Your architecture sound like RPC (remote procedure calls) over HTTP, which is a common form of API.

  2. Probably not. REST is not designed for API's.

  1. Yes, what you describe is an API. Any software interface which is designed to be called by software clients is an API. Your architecture sound like RPC (remote procedure calls) over HTTP, which is a common form of API.

  2. Probably not. REST is not designed for API's. REST is an architectural style optimized for large-scale distributed hypermedia. It is not designed for API's like yours, where a single frontend communicate with a single backend.

Source Link
JacquesB
  • 61k
  • 21
  • 133
  • 187

  1. Yes, what you describe is an API. Any software interface which is designed to be called by software clients is an API. Your architecture sound like RPC (remote procedure calls) over HTTP, which is a common form of API.

  2. Probably not. REST is not designed for API's.