This repository contains the code for the Transaction Service;

This project has been setup to use docker to create a development environment. The readme assumes docker version >= 1.9.1 installed on your system.

The project contains bash scripts to simplify the interaction with docker and enable dynamic code changes. These can be found in

<project_root>/bin

To start up disposable containers use:

bin/start_disposable.sh

The command will attempt to start up containers based on a specific image. If the image cannot be found, it will be downloaded automatically. If the project's image cannot be found, it will be built from the Dockerfile automatically.

When all is complete, you will be taken directly to the shell of the container with the application started for you.

At this point the app will be accessible with base url:

http://localhost:32801/v1

Thus your adventure begins...

simple do ctrl+c to exit the container and the container will also be stopped. However if you're unsure then do:

bin/stop_all.sh

to stop the container explicitly.

Due to the time frame given and the time needed to setup this project, no tests available unfortunately

Base URL : http://localhost:32801/v1

Sample payload for transaction:

{
	"amount": 200,
	"date": "2017-11-29 12:11:00",
	"customer_name": "Lawrence Agbani"
}

The IDs returned in this project are string hashes directly from elastic search. Building an autoincrement sort of thing around it is possible, but then again the time frame was too short to both setup and do all of that.

This project was built using nodejs with restify. The use case needed a lightweight non-blocking endpoint, and looking at how quickly I could bootstrap, I decided to go with nodejs. Bear in mind that this could have also been seemless with GOlang, Java, PHP, etc.

I could have used bare node but decided to go with restify here because of its load management and concurrency. Restify also keeps connections alive which removes the overhead of creating a connection each time when getting called from the same client.

I know it's an overkill at some point but I wanted something that can be run without pain and isn't dependent on what version of what is installed on the local machine. There would have been no need to finish this if it cannot be run.

This is the primary database used in this project. However using elastic search as a primary database is not exactly an ideal use-case for it.