3 ms·
Really, a good API is all that is necessary. Also, maybe an SDK, but I am not particularly enthused by some of the SDKs I encounter, these days. If a service
by ChrisMarshallNY 6y ago
Really, a good API is all that is necessary.
Also, maybe an SDK, but I am not particularly enthused by some of the SDKs I encounter, these days.
If a service can be exposed by a good, basic API that doesn't require (but also affords) an SDK, then this allows development of connectors. Many client packages, these days, are written to allow connectors to be developed.
- asim 6y agoCan you elaborate. What kind of API? Just a HTTP/JSON api?
- ChrisMarshallNY 6y agoI prefer a REST-like API, like Google uses for their services (basically, sending is done with "raw" GET/POST/PUT arguments, instead of blocks of JSON/XML), and Raw/JSON/XML responses. But realistically, some levels of functionality are so intense, you need a “beefier” API, like GraphQL. If that is the case, it might not be a bad idea to review the API. In my opinion, overcomplicated APIs are likely to be the result of the service, trying to exert too much control over the interaction/presentation. Many times, an API is a "back window" or partial view to a more ambitious effort. For example, if the project is a Web-based framework, it will have a lot of rendering and View/Controller functionality that may be of no interest to something like a specialized text editor for content maintenance, so there would be no reason to expose that functionality. It may be a good idea to provide a suite of APIs, as opposed to a single one.
- kgwxd 6y agoFor data-only applications. But if an application wants or needs to promise pixel-perfect results, at the very least, there would need to be a single standard rendering engine.
- ChrisMarshallNY 6y agoI would suggest otherwise. One of the reasons that people choose differing clients, is because they have preferences in how they like the data/process represented. If it is necessary for a team to be "all on the same page," then the management needs to require that everyone use the same rendering client.