IMPLEMENTING
MICROSERVICES
WITH COTE

Armagan Amcalar

Node.js Meetup Berlin
Jun 21st, 2016

Who am I?

Armagan Amcalar
Head of Software Engineering @ unu GmbH
Founder @ Lonca Works

dashersw dashersw

cote
semaver
vieux

pedalboard.js

tartJS
geneJS
jira-bot

AUTHORED ON GITHUB

Outline

Microservices vs monoliths

Problems with microservices

How cote.js can help

Coding demo

Monoliths

Single code base
One process to rule them all
A bug anywhere crashes the whole system
May consume lots of stale resources
Hard to scale; needs even more stale resources
Request–response flow is one huge piece

Easy to manage

Microservices

Separate code base
Multi processes for each service
A bug in a service crashes only that service
Consumes minimal resources
Scales well, needs minimal additional resources

Supports event-driven architecture

Request–response flow breakdown

Hard to manage

Problems of Microservices

Communication between services

Fault-tolerance

Transactional processes

Dynamic service configuration

Service discovery

Health checks & monitoring

Enter cote.js

Zero-configuration

Scalable

Fault-tolerant

Distributed applications

cote.js Features

Auto-discovery
Mesh network, peer-to-peer communication
Pubsub pattern
Requester/responder pattern
Cclient-side communication with Websockets
Load balancing with different strategies
Daemon monitor