Designing an API for service operations with closely related parameters
I’m having trouble deciding how to design this service API.
How does public API designer come to the conclusion what shall be provided for future and what not?
Often working with various jars and exploring the features specially in corner cases, I often realize and think that how is that they thought that it might be a useful scenario somewhere in future that it might be used and an API is made handy. So, how do they come to the conclusion what shall be provided and what not?
Choosing between words with different spellings for function names
A question has been bothering me for a while: when developing international projects, it is common sense to use English as the reference language since it is the language that the most people understand.
How does API design differ from general web application development design? [duplicate]
This question already has answers here: What do great APIs have in common? [closed] (6 answers) Closed 11 years ago. If I was working on a web application designing and writing an API how does that differ from a general web application development? What things would I need to consider and take into account? Are […]
Custom functions in a REST API
Looking at two of our entities Company and Address. A company has a billingAddress and a profileAddress.
Design for using your own API
So I’m planning to use APIs for my host app. But the APIs are built such that it requires a sessionkey for every request.
How to get different resources in a single endpoint in RESTful?
I have a REST webservice that have a couple of resources, like Company and User. But now I need to make a modification to the API to return a special list combining company, user and maybe other type of resource. Like a list of recommendations with various type of resources.
Two libraries connecting to the database, leading to code smell?
In the current company that I work for there is a very large Utilities library. It was written a few years back (long before I joined) and has grown ergonomically over time to now do everything:
Two libraries connecting to the database, leading to code smell?
In the current company that I work for there is a very large Utilities library. It was written a few years back (long before I joined) and has grown ergonomically over time to now do everything:
Two libraries connecting to the database, leading to code smell?
In the current company that I work for there is a very large Utilities library. It was written a few years back (long before I joined) and has grown ergonomically over time to now do everything: