get("/path") { call.respond("Hello") }

val vertx = Vertx.vertx()
		val router = Router.router(vertx)

                router.enableCookies()
		router.enableCORS(allowedMethods = listOf(HttpMethod.GET, <http://HttpMethod.POST|HttpMethod.POST>, HttpMethod.OPTIONS))

   	        router.blockingPost("/login", AccountController::login)
		router.blockingPost("/logout", AccountController::logout)
		router.blockingPost("/account/list", AccountController::list)

fun Router.blockingPost(url: String, handler: KFunction1<@ParameterName(name = "request") RestRequest, RestResponse>) {
	<http://this.post|this.post>(url).handler { rtx ->

		// extract cookies
		val cookies = mutableMapOf<String, String>()
		rtx.cookies().forEach { cookie ->
			cookies.put(key = cookie.name, value = cookie.value)
		}

		// extract body
		rtx.request().bodyHandler { btx ->
			rtx.vertx().executeBlocking<RestResponse>({
				val response = handler.invoke(RestRequest(
					cookies = cookies,
					routingContext = rtx,
					json = String(btx.bytes)))
				it.complete(response)
			}, {
				val response = it.result()
				if (it.succeeded()) {
					if (response.json.isNotBlank()) {
						rtx.response().setStatusCode(200).end(response.json)
					}
				} else {
					RestEasy.log.error(it.cause().message, it.cause())
					rtx.response().setStatusCode(500).end(it.cause().message)
				}
			})
		}
	}
}

For example, systems with a mix of long running transactions and very short transactions are generally the most difficult to tune with any connection pool. In those cases, creating two pool instances can work well (eg. one for long-running jobs, another for “realtime” queries).