All Questions
8
questions
1
vote
1
answer
385
views
Architecting multiple codebases calling our public API + private API for first-party applications
Currently, we have the issue where we have two codebases (API & Website) calling the same database (along with some duplicate business logic) and we want to streamline this so all requests are ...
0
votes
1
answer
2k
views
Exposing complex actions using http verbs in REST API
consider the following REST resource Account
{
number:"number-000",
name: "name",
customer : {},
type : {},
status : "status",
balance : 0,
rating : 0....
2
votes
1
answer
232
views
Keep Hitting 3rd party API or Store Commonly Queried Data In DB?
Colleague and I have begun a long (and hopefully fruitful) project. I've been building and have come to my first crux, and now I ask the experts of the Stack Exchange for their guidance.
I'll keep ...
0
votes
1
answer
277
views
How to Redesign and scale legacy MVC application
I’m working with legacy web app for managing an animal shelter which need to be rearchitected/redesign, so it can scale and be possible to deploy in a central location.
Currently it's physically ...
2
votes
2
answers
217
views
Should a POST endpoint in a REST API allow the inclusion of related resources?
Given the following REST endpoints:
(GET, POST) /api/v2/employer
(GET) /api/v2/employer/{id}
(GET, POST) /api/v2/employer/{id}/employees
Should a consumer of this API have the ability to ...
1
vote
3
answers
648
views
RESTful one or many
What's a good way to design a RESTful URL pattern to get one and many results by ID ?
One (Response: single item)
/invoices?id=a/b
Many (Response: array of items)
/invoices?id=a/b&id=bar
The ...
3
votes
1
answer
364
views
Web API Design advice
I am developing a Web API as services layer for a ASP.NET web forms application.
There are two controllers ContractorController (gives details about the contractor) and PaymentsController (gives ...
3
votes
1
answer
261
views
REST object with resources
I am designing a HTTP-based REST API.
Let's say I have an entity called Entity that has a bunch of properties. Some of its properties are files. Let's say Entity has following properties:
name: ...