Java Abstraction Layer for Cassandra Databases

MAY 21 - 23, 2019
Gaylord National Resort & Convention Center Maryland

Project Casquatch
An Open Source Java Abstraction Layer for
Cassandra Databases.

© DataStax, All Rights Reserved.ConfidentialConfidential © DataStax, All Rights Reserved.
Who am I & Where do I come from?
● Josh Turner
● Principal Engineer @ T-Mobile
● Distributed Data Systems Lead
● Software Development Engineering
/turnerjosh /tdl-jturner

© DataStax, All Rights Reserved.Confidential
Why build it?
● Moving from Oracle™ to Cassandra
● High Learning Curve
● Complex Configuration
● Duplicated Code
● Missing Enterprise Best Practices

Why share it?
● Versatile Framework
● Reduces Learning Curve
● Success Internally In T-Mobile
● Because We Can. #UnCarrier

Why Casquatch?
● Cassandra Is A Name!
● Researched Nicknames
● Sasquatch Is Our Local Legend
● Casquatch Is Born!

What is
Casquatch?
● Cassandra Made Easy!
● Java Abstraction Layer For Cassandra
● Pre-tuned For Enterprise Best Practices
● Object Oriented Code Generation
● Simple Object Based API
● Java Spring Boot Framework Integration

What do I
get?
● Load Balancing / Geo Redundancy
● Connection Pooling
● Reconnection & Retry Policy
● Data Caching
● Workload Filtering
● Security

Open Source
● Open Source Only Model
● T-Mobile Open Source Group
− https://opensource.t-mobile.com
● Project Casquatch
− https://github.com/tmobile/casquatch
● JavaDocs
− https://tmobile.github.io/casquatch/

Open Source
● We recognize that there is a wide range of
platforms, and T-Mobile can't address them
all. This is why we open sourced Casquatch --
we hope the community will be able to expand
how Casquatch is used. As with any tool,
consult with your IT department before using in
production.
● All code samples included are for
demonstration purposes only.
● Licensed under Apache 2.0
− https://www.apache.org/licenses/LICENSE-2.0

Project
History
● 03/05/2018 – 1.0 Internal Release
● 04/05/2018 – 1.1 Release
● 06/22/2018 – 1.2 Release Open Sourced!
● 09/17/2018 – 1.3 Release
● 05/01/2018 – 1.4 Release

How did I get
here?
● We started with Spring Data
● All the testing went great… Until production
● We didn’t know what we didn’t know…
● Tried to fix Spring
● Decided to build and integrate

How does it
compare?
● Spring Data
− No High Availability
− No Retry
− Non Industry Best Practices
● Casquatch
− Highly Available
− Automatic Retry
− Follows Industry Best Practices
● Savings
− Significant reduction in support and design cost
− Highly Reliable Architecture

How much do
I have to
write?
● Spring Data - Developer Effort
− ~150 Lines For Basic Configuration
− ~100 Lines Per Table
− ~10 Tables Per App
● Casquatch - Developer Effort
− ~10 lines of code
● Savings
− 1100+ lines of code and days of developer time
for each application

Code
Generator
● Command Line Interface
● Driven by Table Metadata
● Annotated Objects
● Customizable

Maven
● Hosted by Sonatype
● Available in Maven Central
● Include in pom.xml

Spring Boot
Integration:
● Optional Spring Boot Integration
● Add Import to Application.java
● Dependency Injection
Code For Demonstration Purposes Only

If You Build
It…
● Skip Spring Boot
● Builder Pattern
● CassandraDriver.builder().withUsername() …
.build()
● All properties are available

Spring Boot Configuration:
● Standard application.properties
● The Basics
− Credentials, Contact Points,
Keyspace, etc
● The Advanced
− Connection Limits, LoadBalancing,
Timeout, SSL, etc
● Many More in README.md

Builder Pattern:
● Skip Spring Boot and Do It Yourself
● The Basics
− Credentials, Contact Points,
Keyspace, etc
● The Advanced
− Connection Limits, LoadBalancing,
Timeout, SSL, etc
● Many More in API Docs

Create Schema:
● Create a Cassandra Table
● Columns use _ for spaces
● Supports all data types
● Supports UDT

Create Some Code:
● Run the code generator
● Read in settings on command line
or from properties file
● Configurable options
● More in README.md

Get Some Code: tableName.java
● Custom Package
● Only Required
Imports

● Comments
● Full CQL
● Annotated

● JavaDoc
● Constructors
● Getters and Setters

Get Some Code: pom.xml
● Package option
creates pom.xml
● Snippet shorted for
slide
● Complete Artifact

Use The Code:
● T getById(Class<T> c, T o) : Get by passing an object instance with the key populated.
● void save(Class<T> c, T o) : Save by passing an object instance.
● void delete(Class<T> c, T o): Delete by passing an object instance with the key populated

Demo – Casquatch In 5 Minutes

Java Abstraction Layer for Cassandra Databases

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie Java Abstraction Layer for Cassandra Databases

Ähnlich wie Java Abstraction Layer for Cassandra Databases (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Java Abstraction Layer for Cassandra Databases

Hinweis der Redaktion