pmjones/adr-example

An example ADR subsystem.

adr-example's Issues

Responding in Various Formats

@pmjones Quick question but I thought I'd ask it here for everyone's benefit.

When responding with the same payload but in more than 1 format (for instance, user may request JSON, CSV, or XML), how would you structure your responder classes?

Some options I'm considering (and caveats):

1. Have abstract JSON, CSV, and XML responders. (Possible inheritance hell)
2. Make each responder handle all possible formats. (Huge responders, likely code repetition)
3. Use traits for serializing payloads to each format. (Only allows for generic serialization, no custom logic per responder)
4. Become a graphic designer. (More free time but even fewer problems with concrete answers)

Poor domain logic

Hey @pmjones the example it's well structured and easy to understand, but i think this it's not a real domain with real complex logic.
Are you planning to do some real-world and handle some domain complexity?
If help needed ping me 😄

Using ADR, where would I build a complex page with multiple data and cached items?

I'm trying to build a dashboard for the user (after logging in), in that dashboard the user can see his data, and I also calculate some data and would want to cache that before returning it to the user.

Where would all this logic happen? Following ADR?