Skip to main content

New answers tagged

3 votes

REST API with swappable backends

Your last 2 paragraphs are the way to go. No real overhead, especially if you cache any client specific meta data associated with each call. Most likely you will have to write a façade for each back ...
LoztInSpace's user avatar
  • 1,199
0 votes

Separate unidirectional streams vs single bidirectional stream

It's easier to specify a pair of uni-directional streams rather than a bi-directional stream. In theory, one needs to define the interactions between the function calls in both directions (both reads ...
Cort Ammon's user avatar
  • 11.6k
0 votes

Separate unidirectional streams vs single bidirectional stream

Superfluously, unidirectional streams come with a smaller surface but bidirectional streams come with fewer objects to handle. In the end, this is mostly a matter of personal preference of broad ...
MisterMiyagi's user avatar
7 votes

Separate unidirectional streams vs single bidirectional stream

One use case for a bidirectional stream is when editing files. This would often require both reading and writing, and editing files is a quite common use case. I also believe most OSes exposes files ...
JonasH's user avatar
  • 5,824
7 votes
Accepted

Separate unidirectional streams vs single bidirectional stream

In languages where the interface for a stream is inherently bidirectional (see C#'s Stream for example), this can lead to bugs when the wrong stream is accidentally used. I agree. That's why there ...
freakish's user avatar
  • 1,926
3 votes

How to handle data when source of truth is through API

This is an extremely common problem when building any sort of distributed system. This is such a foundational problem for service-oriented architecture and microservices that no single canonical term ...
Greg Burghardt's user avatar

Top 50 recent answers are included