muskanmahajan37 / kotlin-ktor-exposed-starter Goto Github PK

Updated for Kotlin 1.4.0 and Ktor 1.4.0

Companion article: https://ryanharrison.co.uk/2018/04/14/kotlin-ktor-exposed-starter.html

1. Clone the repo.
2. In the root directory execute ./gradlew run
3. By default the server will start on port 8080. See below Routes section for more information.

• Ktor - Kotlin async web framework
• Netty - Async web server
• Exposed - Kotlin SQL framework
• H2 - Embeddable database
• HikariCP - High performance JDBC connection pooling
• Jackson - JSON serialization/deserialization
• JUnit 5, AssertJ and Rest Assured for testing

The starter project creates a new in-memory H2 database with one table for Widget instances.

As ktor is async and based on coroutines, standard blocking JDBC may cause performance issues when used directly on the main thread pool (as threads must be reused for other requests). Therefore, another dedicated thread pool is created for all database queries, alongside connection pooling with HikariCP.

GET /widget --> get all widgets in the database

GET /widget/{id} --> get one widget instance by id (integer)

POST /widget --> add a new widget to the database by providing a JSON object (converted to a NewWidget instance). e.g -

{
    "name": "new widget",
    "quantity": 64
}

returns

{
    "id": 4,
    "name": "new widget",
    "quantity": 64,
    "dateCreated": 1519926898
}

PUT /widget --> update an existing widgets name or quantity. Pass in the id in the JSON request to determine which record to update

DELETE /widget/{id} --> delete the widget with the specified id

All updates (creates, updates and deletes) to Widget instances are served as notifications through a WebSocket endpoint:

WS /updates --> returns Notification instances containing the change type, id and entity (if applicable) e.g:

{ 
    "type": "CREATE", 
    "id": 12, 
    "entity": { 
      "id": 12, 
      "name": "widget1", 
      "quantity": 5, 
      "dateUpdated": 1533583858169 
    }
}

The sample Widget service and corresponding endpoints are also tested with 100% coverage. Upon startup of the main JUnit suite (via the test source folder), the server is started ready for testing and is torn down after all tests are run.

• Unit testing of services with AssertJ - DAO and business logic
• Integration testing of endpoints using running server with Rest Assured - routing tests/status codes/response structure