This is a training project, and code should probably not be used in production.

The aim of this project will be to provide a small component, of a micro-services oriented architecture, that will be able to keep time. All other services in the system will rely on our service to ensure we have the same idea of time, making it critical.

Despite common sense and logic, we will structure our service following REST principles.

Please read the Contribution guideliens.

• Provide the basic service with:
  • GET api/time - returning the current time as a text string
  • GET api/date - returning the current date as a text string

See open issues here: https://github.com/avodovnik/qsec-time-service/milestone/1

• We will introduce a bit more complexity, and the service will be abl to update the time and date.
• Initially, we'll only let that live for the duration of the service, but we want to persist the time skew later.

• Service should, at this point, handle scale out scenarios, i.e. working correctly with above requirements even if server runs on many processes and/or many machines.

When we're feature-complete for a single version, we'll create a new branch, called release/{version} which will serve as our source of truth for that version. We are following the VSTS strategy for trunk based deployment.