The airports from ysukhoverkhov

airports's Introduction

The following tools are required:

In the project's root folder, execute:

In the project's root folder, execute:

Open the browser at localhost:8080

Pure FP approach (to encode as much proves in code as possible and to couple components as less as possible)
Algebras implemented as tagless-final (because less boilerplate comparing to Free)
DI as nested algebras (because it's obvious)
Common algorithms extracted in a shared project (because it's common sense)
Elm for UI (without any particular reasons)
Property based tests where appropriate (to make sure particular algebras are defined on the whole domain)
No mocking library in tests (because they suck), dedicated implementations of various low level algebras instead

GET /health/alive - 200 - "OK" all the time
GET /health/ready - 200 - "OK" when data is read and service is ready to serve requests
GET /api/airports/<country> - Query for airports pert country
GET /api/report/runways - Query for runways types per countries
GET /api/report/topcountries - Query for TOP and bottom countries per airports

UI is ugly (very!)
Error handling is not verbose
CSV parser is super slow
Reports/Queries are performed on data in memory, so no handling for bigger data. But could be changed to any SQL/NoSQL with easy
Property based tests mixed with unit tests, could not be suitable for large scale project
Elm project is injected in a hacky way (without proper sbt-web project)
Some version incompatibility in libs
Web Service lacks contract testing

Recommend Projects