Event driven microservices with vxms, hazelcast and kubernetes - muenchen

BASEL BERN BRUGG DÜSSELDORF FRANKFURT A.M. FREIBURG I.BR. GENF
HAMBURG KOPENHAGEN LAUSANNE MÜNCHEN STUTTGART WIEN ZÜRICH
Event-driven microservices with
Vxms, Hazelcast and Kubernetes
Andy Moncsek
Senior Consultant
Andy.Moncsek@trivadis.com
Twitter: @AndyAHCP

Agenda
2 23.02.2018
1. Vert.x / Vxms
2. Kubernetes
3. Configure Hazelcast to run in Kubernetes
4. Demo
5. Conclusion
Event-driven microservices with Vxms, Hazelcast and Kubernetes

Vert.x / Vxms
3 23.02.2018 Event-driven microservices with Vxms, Hazelcast and Kubernetes

What Vert.x is
is a tool-kit for building
reactive appications on the JVM

What Vert.x is
is the default cluster provider
of Vert.X

What Vxms is
Vxms* is an opinionated framework
on top of Vert.x for building reactive
appications on the JVM
* http://amoahcp.github.io/vxms/

Design goals
7 23.02.2018 Vert.x based microservices with vxms
easy to use
100% Vert.x
compatible
ResilienceModularity
no blaming

Vert.x example
Event-driven microservices with Vxms, Hazelcast and Kubernetes8 23.02.2018
public class Gateway extends AbstractVerticle {
@Override
public void start(Future<Void> startFuture) throws Exception {
Router router = Router.router(vertx);
router.get("/helloEventbus/:name").handler(ctx -> {
String name = ctx.request().getParam("name");
vertx.eventBus().send("/hello", name, responseHandler -> {
Message<String> result = responseHandler.result();
ctx.response().end(result.body());
});
});
JsonObject config = vertx.getOrCreateContext().config();
vertx.createHttpServer().requestHandler(router::accept)
.listen(config.getInteger("port", 9090), config.getString("host", "localhost"));
startFuture.complete();
}
}
• Create rest endpoint
• Send to eventbus
• Pass response to rest reply

What Vxms is
@ServiceEndpoint
public class Gateway extends VxmsEndpoint{
@Path("/helloEventbus/:name")
@GET
public void simpleEventbusCall(RestHandler handler) {
String name= handler.request().param("name");
handler.
eventBusRequest().
send("/hello", name).// send message to eventbus, pass result to REST response
mapToStringResponse((message, response)->
response.complete(message.result().body()).
execute();// execute non blocking
}
}

What Vxms is
@ServiceEndpoint
public class Gateway extends VxmsEndpoint{
@Path("/helloEventbus/:name")
@GET
public void simpleEventbusCall(RestHandler handler) {
String name= handler.request().param("name");
handler.
eventBusRequest().
send("/hello", name).
mapToStringResponse((message, response)->
response.complete(message.result().body()).
}
}
@ServiceEndpoint
public class EventbusExample extends VxmsEndpoint{
@Consume("/hello")
public void simpleNonBlocking(EventbusHandler handler) {
String name= handler.request().body();
handler.
response().
stringResponse((response)->
response.complete("hello World "+name)).// complete non-blocking response
timeout(2000).// timeout for stringResponse handling
onError(error->LOG(error.getMessage())).
onFailureRespond((error, future)->future.complete("error:"+error.getMessage())).
retry(3).
closeCircuitBreaker(2000).
}
}
Event via Hazelcast

Kubernetes

Kubernetes basics: What it is....
 Kubernetes is platform designed to automate deploying,
scaling, and operating application containers.
 Deploy your applications quickly and predictably.
 Scale your applications on the fly.
 Roll out new features seamlessly.

Kubernetes Namespaces
”virtual" cluster
Separates DEV, TEST, PROD, ... environments

Kubernetes Pods
Group of containers
Shares network/namespace/ IP
Shares environmental variables
Shared volumes

Kubernetes Controller
15 23.02.2018
Ensure X pods are running
Pod templates
Rolling update

Kubernetes Services
16 23.02.2018
Pod discovery
IP per service
1-N port numbers
Route to pods
Load balancer

Configure Hazelcast to run in
Kubernetes

Hazelcast & Kubernetes  What we want
Case 1: Lookup all nodes (Verticles) managed by one controller
 1 – N pods
 1 – X container
Case 2: Lookup all nodes/services in a cluster / namespace
 N services per cluster
Routing to X pods

Hazelcast & Kubernetes  What we get
Easy scale- up/down of service instances
Failover provided by Kubernetes and Hazelcast
Distributed Event-Bus  each Verticle instance
Replicated shared data

Hazelcast node discovery in Kubernetes
20 23.02.2018
Hazelcast discovery plugin for Kubernetes
Option 1: Kubernetes REST API
Allows discovery by service name
Option 2: DNS Lookup
Enable custom cluster.xml in Vert.X  put to classpath
https://github.com/hazelcast/hazelcast-kubernetes

Vert.x / Hazelcast node discovery in Kubernetes
21 23.02.2018
Hazelcast
<hazelcast>
…
<discovery-strategy enabled="true"
class=”….HazelcastKubernetesDiscoveryStrategy">
<properties>
<property name="service-label-name">cluster1</property>
<property name="service-label-value">true</property>
<property name="namespace">default</property>
</properties>
</discovery-strategy>
</hazelcast>
• Partition your cluster using
labels
Hazelcast.xml / Cluster.xml
kind: Service
apiVersion: v1
metadata:
labels:
service-label-name: cluster1
service-label-value: true
Kubernetes

Demo

Conclusion
Docker IS mainstream
Kubernetes dominates the orchestration market
Hazelcast is an easy to use & fast solution for
Storage, caching, messaging & more
Works well in cloud environments
Vert.x is a fast & powerful toolkit for reactive applications
Vxms reduces the complexity of Vert.x

References
- https://github.com/amoAHCP/vxms
- http://vertx.io
- https://maven.fabric8.io
- https://github.com/hazelcast/hazelcast-kubernetes
- http://docs.hazelcast.org/docs/latest-
development/manual/html/Setting_Up_Clusters/index.html
- http://www.lihaoyi.com/post/StrategicScalaStylePrincipleofLeastPower.html

Thank you
Andy Moncsek
Senior Consultant
Andy.Moncsek@trivadis.com
Twitter: @AndyAHCP
23.02.201826 Event-driven microservices with Vxms, Hazelcast and Kubernetes

Introduction

What Vert.x is
28 23.02.2018
scale polyglot
general purposefun

Design goals
No Vert.x
blaming
• just an other
focus (create
services)
Easy of use
• Vert.x is very
powerful /
concepts are
still new*
100%
compatible
• to Vert.x

Design goals
Resilience
• APIs to build
resilient
applications must
be 1st class citizens
Modularity
• Vxms-core
• Vxms-rest
• Vxms-event
• Vxms-K8s-discovery

Typical microservice architecture

Why?
 Idea
 Avoid Service registry & lookup
 Decouple services  async + events
 Fast re-/deploy
 And more: resilient,…

Event-driven microservice
 Using an in-memory data grid
 Automatic node lookup (services)
 Failover
 Shared data  replicated in cluster
 Pub / sub
 Request / response
 NO (active) Service discovery

Event driven microservices with vxms, hazelcast and kubernetes - muenchen

More Related Content

What's hot

Similar to Event driven microservices with vxms, hazelcast and kubernetes - muenchen

More from Andy Moncsek

Recently uploaded

Event driven microservices with vxms, hazelcast and kubernetes - muenchen