cathalmchale/ray

The Ray Tracer Challenge in .NET Core

ray's Issues

Stand-up a rendering API

Background

Would like to be able to document the use of this Ray Tracer app imperatively.
Best way to do this, I feel, is:

• Use Docker to virtualize the run-time environment.
• Stand-up an API (Json Rest) that will exercise the Ray Tracer like calling directly from code.

Now documentation can be as simple as:

• Docker build command.
• Docker run command (or potentially Docker-compose).
• Fire this Json at an endpoint to generate an image.

Next Steps

Have the DTOs written that will define the Json API. I now need to turn the Json information into a Ray.Domain World that can be passed to the renderer. To do this, I need a number of simple Factories that will interrogate the Json (C# DTOs) and spit out instantiated objects.

Put simply - I need a place for this logic. It doesn't belong in Ray.Domain and I'll strive to keep the Web API layer very thin. So where should it go?
I think a Ray.Command layer will suffice. However, then we have to consider the infrastructure code that goes with this (Command Pattern interfaces and plumbing). I've written it loads of times before, but first I decided to check Nuget and Google.

MS patterns wiki

Discusses the Mediator pattern being used as a pipeline for the Commands/Handlers. This pointed me to a Nuget package by the trusted Jimmy Bogard (AutoMapper).

MediatR 3

I'm immediately convinced that I'll use this, rather than roll my own!