Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microservices with Clojure

You're reading from   Microservices with Clojure Develop event-driven, scalable, and reactive microservices with real-time monitoring

Arrow left icon
Product type Paperback
Published in Jan 2018
Publisher Packt
ISBN-13 9781788622240
Length 336 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Anuj Kumar Anuj Kumar
Author Profile Icon Anuj Kumar
Anuj Kumar
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Monolithic Versus Microservices 2. Microservices Architecture FREE CHAPTER 3. Microservices for Helping Hands Application 4. Development Environment 5. REST APIs for Microservices 6. Introduction to Pedestal 7. Achieving Immutability with Datomic 8. Building Microservices for Helping Hands 9. Configuring Microservices 10. Event-Driven Patterns for Microservices 11. Deploying and Monitoring Secured Microservices 12. Other Books You May Enjoy

Datomic architecture


Datomic is a distributed database that supports ACID (http://docs.datomic.com/acid.html) transactions and stores data as immutable facts. Datomic is focused on providing a robust transaction manager to keep the underlying data consistent, a data model to store immutable facts, and a query engine to help retrieve data as facts over time. Instead of having its own storage, it relies on an external storage service (http://docs.datomic.com/storage.html) to store the data on disk.

Datomic versus traditional database

A typical database is implemented as a monolithic application that contains the storage engine, query engine, and the transaction manager all packaged as a single application to which clients connect to store and retrieve data. Datomic, on the other hand, takes a radical approach of separating out the Transaction Manager (Transactor) as a separate process to handle all the transactions and commit the data to an underlying Storage Service that acts as a persistence...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image