# Apache Cassandra in a Microservices Enterprise Platform

DevFeed: [Apache Cassandra in a Microservices Enterprise Platform](<https://devfeed.tech/articles/apache-cassandra-in-a-microservices-enterprise-platform-31994.md>)

Original publisher: [Read original article](<https://tech.finn.no2015/04/28/Apache-Cassandra-in-a-Microservices-Enterprise-Platform/>)

Author: mick

Published: 2015-04-28T14:00:00Z

Content type: article

Language: en

Sources: [Finn.no](<https://devfeed.tech/sources/finn-no.md>)

Topics: [Apache Cassandra](<https://devfeed.tech/topics/cassandra.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Temporal data](<https://devfeed.tech/topics/temporal-data.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cassandra](<https://devfeed.tech/tags/cassandra.md>), [coupling](<https://devfeed.tech/tags/coupling.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [rest](<https://devfeed.tech/tags/rest.md>), [time-series](<https://devfeed.tech/tags/time-series.md>)

## AI overview

The article discusses Apache Cassandra as a persistence layer for microservices platforms, particularly for systems that need scalability and time-series data models. It also outlines microservices practices involving isolated runtime APIs, reduced coupling, REST, and producer-defined schemas for event-driven designs.

## Source excerpt

In this article we'll explore how Apache Cassandra, the world's most popular wide column store and 8th most popular database overall, will only grow as a cornerstone technology in a microservices platform. With a little theory to microservices, to some examples of microservices and underlying required infrastructure, we'll show that any solution both capable of scaling and dealing with time-series data-models is going to need to depend upon Apache Cassandra as a persistence layer, despite having a polyglot persistence model at large. microservices Microservices is a term that's come out of ThoughtWorks' Martin Fowler and James Lewis. It's a bit of a buzzword, basically a fresh revival of the parts of service orientated architecture that you should be focusing on and getting right. A lot of it hopefully is obvious to you already. If you've been doing service orientated architecture or even generally just unix programming properly over the years it might well be frustrating just how buzz "microservices" has become. But it's worth keeping in mind how much garbage we've collected and how many aspects of service orientated architecture that we've gotten badly wrong over the years. Younger programmers certainly deserve the clarity that ThoughtWorks is giving us here. Microservices, following the tips and guidelines from Sam Newman, can basically be broken down into four groups. interfaces Ensure that you standardise the systems architecture at large and especially the gaps or what we know as the APIs between services. Standardise upon practices and protocols that minimise coupling. Move from tightly coupled systems with many compile time dependencies and distributed published client libraries, to clearly defined and isolated runtime APIs. Take advantage of REST, especially level 3 in richardson's maturity model, for the synchronous domain driven designed parts of your system. When it comes to event driven design use producer defined schemas, like that offered by Apache Th