Skip to main content

New answers tagged

0 votes

API supporting multiple authentication providers?

I would do the second option so each API only has to understand one token. That said, I would probably also go with a 3rd party identity (token) provider that can take care of a lot of this kind of ...
LoztInSpace's user avatar
  • 1,338
7 votes
Accepted

What is a good approach to sync remote API data to a database?

'As fresh as reasonably possible' is not a concrete requirement and, as such, is not useful. I would start by flipping your thinking around to the question: 'what level of staleness is tolerable?' ...
JimmyJames supports Canada's user avatar
3 votes

What is a good approach to sync remote API data to a database?

The simplest way is often the best. Here you can simply make api calls periodically, populate a staging table on your db and then switch it with the old table. The delta approach, where you make a ...
Ewan's user avatar
  • 81.9k
0 votes

Api Best practices (conventions and separation of concerns )

I appreciate any guidance on how to structure these controllers in a coherent and maintainable manner. You design your API like you would design a class library for a developer. That is your target ...
nvoigt's user avatar
  • 9,185
0 votes

Api Best practices (conventions and separation of concerns )

Assuming you are working with CRUD especially HTTP POST hides parameters but is very useful when handling JSON, like a parameter class with fields. Per domain / entity / controller starting with circa ...
Joop Eggen's user avatar
  • 2,541
0 votes

Api Best practices (conventions and separation of concerns )

Advice on APIs When defining an API don't let any one implementation dictate how that API is laid out or works. An implementation framework/library/etc... that is worth its salt will allow you to ...
Kain0_0's user avatar
  • 16.5k

Top 50 recent answers are included