はてなブックマーク

This discovery bridge imports services from Kubernetes (or Openshift v3) into the Vert.x service discovery. Kubernetes services are mapped to Record. This bridge only supports the importation of services from kubernetes in vert.x (and not the opposite). Record are created from Kubernetes Service. The service type is deduced from the service.type label. If not set, the service is imported as unknow

Docker lets you deploy applications inside lightweight and isolated software containers. Applications run side by side in isolated Linux containers. If you never used Docker before check this online tutorial. Vert.x provides Docker images that you can use to run your applications. Two Docker images are provided: vertx/vertx4 is the base image you need to extend to run your own application vertx/ve

At the heart of Vert.x is a set of Java APIs that we call Vert.x Core Writing TCP clients and servers Writing HTTP clients and servers including support for WebSockets The Event bus Shared data - local maps and clustered distributed maps Periodic and delayed actions Deploying and undeploying Verticles Datagram Sockets DNS client File system access Virtual threads High availability Native transport

public class Server extends VerticleBase { public Future<?> start() { return vertx.createHttpServer() .requestHandler(req -> req.response() .putHeader("content-type", "text/plain") .end("Hello from Vert.x!") ) .listen(8080); } } class Server : VerticleBase() { override fun start(): Future<*> { return vertx.createHttpServer() .requestHandler { req -> req.response() .putHeader("content-type", "text/