Baratine in Practice

1

Baratine in Practice

Nam NguyenSoftware Engineer

Caucho Technology, Inc.

Date: 2014-06-17Location: San Diego JUG

2

Baratine in PracticeDownloadInstallOur first @ResourceService

- @Modify- Multiple counters

Concepts@Service

- implement an example @Workers

- implement an exampleType of services chartPartitioning and clustering

3

Task: Baratine quick start

- Download- Install- Our first service

http://doc.baratine.io/v0.8/manual/quick-start/

@Journal@ResourceService(“public:///counter/{_id}”)public class CounterServiceImpl{ private long _id; private long _counter; public long get() { return _counter; }

@Modify public long incrementAndGet() { return ++_counter; }

@Modify public long decrementAndGet() { return --_counter; }

@Modify public long addAndGet(long value) { _counter = _counter + value;

return _counter; }}

INBOX

JOURNALKEY-VALUE DB

(internal)

4

OUTBOXHTTP Polling

HTTP REST

WebSocket

Java

5

What You Get

+ Insane low-latency concurrent performance

assign thread1. incrementAndGet()2. incrementAndGet()3. addAndGet()4. decrementAndGet()5. incrementAndGet()

assign thread6. incrementAndGet()7. ...

NO BLOCKING / LOCKING ! very CPU cache friendly (for both data and instructions)

Batch A

Batch B

• CPU core uninterrupted during batch• no context switching• no pausing• thread screams through entire batch

6

Batch Programming

assign thread@BeforeBatch

1 incrementAndGet()2. addAndGet()3. addAndGet()4. decrementAndGet()5. incrementAndGet()6. incrementAndGet()

@AfterBatch- flush writes

assign thread@BeforeBatch7. ...

Leave expensive operations to be executed at the end of the batch.

Inbox is empty at this point

7

Performance Characteristics

1 2 4 8 16 32Batch Size / Clients

Requests per Second

Baratine

8

Performance Characteristics

1 2 4 8 16 32Batch Size / Clients

Requests per Second

Baratine

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ServiceA to ServiceB within the same JVM

9

Reliable to Batch

assign thread@BeforeBatch

1 incrementAndGet()2. addAndGet()3. addAndGet()4. decrementAndGet()5. incrementAndGet()6. incrementAndGet()

@AfterBatch- flush writes

assign thread@BeforeBatch

7. ...

Safe to process in batches.

@OnCheckpoint

10

Putting it All Together

Freed to operatein memory safely!

▲ Operational Data

11

@Journal@ResourceService(“public:///counter/{_id}”)public class CounterServiceImpl{ private long _id; private long _counter; public long get() { return _counter; }

@Modify public long incrementAndGet() { return ++_counter; }

@Modify public long decrementAndGet() { return --_counter; }

@Modify public long addAndGet(long value) { _counter = _counter + value;

return _counter; }}

12

@Service

Barebones service, basis of @ResourceServiceSingleton, only one instance within a JVM

- No @Modify- No automatic restore- No automatic paging- No automatic checkpointing- No automatic query support- No automatic partitioning

Warning: hardcore!

13

@Service

Less magic: you have fine-grained control

+ @Journal+ @OnRestore+ @OnCheckpoint+ @OnActive+ @BeforeBatch+ @AfterBatch

14

Task: implement a logging service with a @Service

15

@Workers

A @Service with a thread-pool acting on the inbox. Example: hibernate, SAP, MySQL, legacy, integration

- Does not fully benefit from batching- Not single-threaded

+ Can block+ Multi-threaded

16

Task: implement a @Workers @Service

17

Types of ServicesAnnotation: @ResourceService @Service @Workers

Batching ✓ ✓ ✓*

Journaling ✓ ✓Checkpointing ✓ ✓

Paging ✓Partitioning ✓

Resource ID’s ✓Search ✓

Threaded-ness single single multi

Can Block? ✓Performance ★★★☆ ★★★★ ★☆☆☆

(manual)

18

Partitioning and Clustering

/auction/111/auction/444/auction/999

/auction/222/auction/555/auction/888

/auction/000/auction/333/auction/666/auction/777

192.168.1.100

192.168.1.102

192.168.1.101

Resources are partitionedby its service URL and ID

19

State of Baratine

GPL

Been in active development for over 2 years

v0.8.3 (alpha)

http://baratine.io (alpha)

Thank you!

stealth<

20

The End

Q and A