All Questions
21
questions
0
votes
1
answer
475
views
Is it okay to combine bff and rest api?
I'm building an application related to donation on streams.
And I have such models as "alert" and "alert-template".
"alert" is a set of different parameters to understand ...
- 149
3
votes
2
answers
2k
views
Communication between two apps
I am thinking of creating two applications, one of which (App 1) will be in Django (DRF) and other (App 2)might be Django but might be another more lightweight framework (maybe Flask or plain Django ...
- 161
0
votes
2
answers
234
views
Structuring optional REST resource hierarchy
I am designing a REST service with multiple end points which will be servicing the following hierarchy:
Department has many Category Groups
Category Group has many Category(-ies)
Category has many Sub-...
- 183
1
vote
2
answers
131
views
Photo Library Service: What should be right way of photo library using AWS S3 and Java
I want to make a service that is supposed to upload Photos in S3 and make them available using a link.
I have few design plans for my service.
PLAN 1:
Upload photo to my REST API which will update ...
- 113
1
vote
2
answers
2k
views
Incorporate a background job enqueue endpoint in a REST API
To exchange data between our standalone frontend application and the backend API, we currently have a REST API, with standard endpoint to list/create/update/destroy ressources with a consistent naming ...
- 147
1
vote
2
answers
2k
views
REST API Client Library Design
I'm working on a reusable client library to abstract a REST endpoint that we use in many of our in-house applications. It is actually split into 3 APIs, and certain endpoints/resources require ...
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....
- 271
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 ...
- 129
-1
votes
1
answer
80
views
APIs: Many minimal ones or a few bigger
I'm currently working on a project/product which consists of ~60 REST APIs and one client (Web app)
I find many downsides on this design, and not so many benefits, and I'd like to know if this is ...
user254856
2
votes
0
answers
83
views
API Architecture Decision on Authorization & Validation levels
We are designing an authorization mechanism for a Product API where users have their own claims.
The api has a patch request like this:
PATCH https://product-fcd.com/api/product -d {"Products": []} -...
- 121
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 ...
- 393
32
votes
4
answers
12k
views
Microservices and data storage
I'm considering moving a monolithic REST API to a microservice architecture, and I'm getting a bit confused about data storage.
As I see it, some of the benefits of microservices would be:
...
- 429
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,017
2
votes
3
answers
1k
views
How to tie the request filters to the data model in a REST API
I am trying to build a RESTful search api (POST request) that can return different types of resources (e.g A, B, C, etc). I have defined a data model for each of the resource type. There are some ...
- 653
2
votes
1
answer
1k
views
REST API design: distinction between searching and getting all instances of a resource
At the moment, my (pretty standard) REST interface looks like this:
POST /foo # creates a new foo
PUT /foo/{id} # updates a specific foo
GET /foo/{id} # returns a specific foo
GET /...
- 255