Alternatives to Datomic Cloud logo

Alternatives to Datomic Cloud

Amazon DynamoDB, Cloud Firestore, Azure Cosmos DB, Google Cloud Datastore, and Google Cloud Bigtable are the most popular alternatives and competitors to Datomic Cloud.
6
7
+ 1
0

What is Datomic Cloud and what are its top alternatives?

A transactional database with a flexible data model, elastic scaling, and rich queries. Datomic is designed from the ground up to run on AWS. Datomic leverages AWS technology, including DynamoDB, S3, EFS, and CloudFormation to provide a fully integrated solution.
Datomic Cloud is a tool in the NoSQL Database as a Service category of a tech stack.

Datomic Cloud alternatives & related posts

Amazon DynamoDB logo

Amazon DynamoDB

1.9K
1.2K
163
1.9K
1.2K
+ 1
163
Fully managed NoSQL database service
Amazon DynamoDB logo
Amazon DynamoDB
VS
Datomic Cloud logo
Datomic Cloud

related Amazon DynamoDB posts

Julien DeFrance
Julien DeFrance
Principal Software Engineer at Tophatter | 16 upvotes 905.9K views
atSmartZipSmartZip
Rails
Rails
Rails API
Rails API
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Capistrano
Capistrano
Docker
Docker
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
MySQL
MySQL
Amazon RDS for Aurora
Amazon RDS for Aurora
Amazon ElastiCache
Amazon ElastiCache
Memcached
Memcached
Amazon CloudFront
Amazon CloudFront
Segment
Segment
Zapier
Zapier
Amazon Redshift
Amazon Redshift
Amazon Quicksight
Amazon Quicksight
Superset
Superset
Elasticsearch
Elasticsearch
Amazon Elasticsearch Service
Amazon Elasticsearch Service
New Relic
New Relic
AWS Lambda
AWS Lambda
Node.js
Node.js
Ruby
Ruby
Amazon DynamoDB
Amazon DynamoDB
Algolia
Algolia

Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

Future improvements / technology decisions included:

Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

See more
Dmitry Mukhin
Dmitry Mukhin
CTO at Uploadcare | 15 upvotes 95.4K views
atUploadcareUploadcare
Google App Engine
Google App Engine
Python
Python
Redis
Redis
Amazon S3
Amazon S3
Amazon DynamoDB
Amazon DynamoDB
PostgreSQL
PostgreSQL

Uploadcare has built an infinitely scalable infrastructure by leveraging AWS. Building on top of AWS allows us to process 350M daily requests for file uploads, manipulations, and deliveries. When we started in 2011 the only cloud alternative to AWS was Google App Engine which was a no-go for a rather complex solution we wanted to build. We also didn鈥檛 want to buy any hardware or use co-locations.

Our stack handles receiving files, communicating with external file sources, managing file storage, managing user and file data, processing files, file caching and delivery, and managing user interface dashboards.

At its core, Uploadcare runs on Python. The Europython 2011 conference in Florence really inspired us, coupled with the fact that it was general enough to solve all of our challenges informed this decision. Additionally we had prior experience working in Python.

We chose to build the main application with Django because of its feature completeness and large footprint within the Python ecosystem.

All the communications within our ecosystem occur via several HTTP APIs, Redis, Amazon S3, and Amazon DynamoDB. We decided on this architecture so that our our system could be scalable in terms of storage and database throughput. This way we only need Django running on top of our database cluster. We use PostgreSQL as our database because it is considered an industry standard when it comes to clustering and scaling.

See more

related Cloud Firestore posts

fontumi
fontumi
Firebase
Firebase
Node.js
Node.js
FeathersJS
FeathersJS
Vue.js
Vue.js
Google Compute Engine
Google Compute Engine
Dialogflow
Dialogflow
Cloud Firestore
Cloud Firestore
Git
Git
GitHub
GitHub
Visual Studio Code
Visual Studio Code

Fontumi focuses on the development of telecommunications solutions. We have opted for technologies that allow agile development and great scalability.

Firebase and Node.js + FeathersJS are technologies that we have used on the server side. Vue.js is our main framework for clients.

Our latest products launched have been focused on the integration of AI systems for enriched conversations. Google Compute Engine , along with Dialogflow and Cloud Firestore have been important tools for this work.

Git + GitHub + Visual Studio Code is a killer stack.

See more
Pran B.
Pran B.
Fullstack Developer at Growbox | 6 upvotes 48.2K views
Flutter
Flutter
Cloud Firestore
Cloud Firestore
SQLite
SQLite

Goal/Problem: A small mobile app (using Flutter ) for saving data offline ( some data offline) and rest data need to be synced with Cloud Firestore Tools: Cloud Firestore , SQLite Decision/Considering/Need suggestions: There is no state management in the app yet. There is a requirement to store some data offline and it should be available easily (when the phone is offline) and some data needs to stored in the cloud. I am considering using sqlflite for phone storage and firestore to sync and manage the online database. I am using flutter to build the app, I couldn't find a reliable way to use firestore cache for reading the data when phonphone is offline. So I came up with the above solution. Please suggest is this good?

See more
Google Cloud Bigtable logo

Google Cloud Bigtable

65
68
12
65
68
+ 1
12
The same database that powers Google Search, Gmail and Analytics
Google Cloud Bigtable logo
Google Cloud Bigtable
VS
Datomic Cloud logo
Datomic Cloud
Cloudant logo

Cloudant

32
33
20
32
33
+ 1
20
Distributed database-as-a-service (DBaaS) for web & mobile apps.
Cloudant logo
Cloudant
VS
Datomic Cloud logo
Datomic Cloud

related Cloudant posts

Josh Dzielak
Josh Dzielak
Developer Advocate at DeveloperMode | 5 upvotes 92K views
Firebase
Firebase
Pouchdb
Pouchdb
CouchDB
CouchDB
Cloudant
Cloudant

As a side project, I was building a note taking app that needed to synchronize between the client and the server so that it would work offline. At first I used Firebase to store the data on the server and wrote my own code to cache Firebase data in local storage and synchronize it. This was brittle and not performant. I figured that someone else must have solved this in a better way so I went looking for a better solution.

I needed a tool where I could write the data once and it would write to client and server, and when clients came back on line they would automatically catch the client up. I also needed conflict resolution. I was thrilled to discover Pouchdb and its server-side counterpart CouchDB. Together, they met nearly all of my requirements and were very easy to implement - I was able to remove a ton of custom code and have found the synchronization to be very robust. Pouchdb 7 has improved mobile support too, so I can run the app on iOS or Android browsers.

My Couchdb instance is actually a Cloudant instance running on IBM Bluemix. For my fairly low level of API usage, it's been totally free, and it has a decent GUI for managing users and replications.

See more
Amazon SimpleDB logo

Amazon SimpleDB

15
22
0
15
22
+ 1
0
Highly available and flexible non-relational data store
    Be the first to leave a pro
    Amazon SimpleDB logo
    Amazon SimpleDB
    VS
    Datomic Cloud logo
    Datomic Cloud
    Firebase Realtime Database logo

    Firebase Realtime Database

    14
    6
    0
    14
    6
    + 1
    0
    Store and sync data in real time
      Be the first to leave a pro
      Firebase Realtime Database logo
      Firebase Realtime Database
      VS
      Datomic Cloud logo
      Datomic Cloud
      restdb.io logo

      restdb.io

      10
      13
      1
      10
      13
      + 1
      1
      A plug and play database service for the web and beyond
      restdb.io logo
      restdb.io
      VS
      Datomic Cloud logo
      Datomic Cloud
      CloudBoost logo

      CloudBoost

      7
      17
      10
      7
      17
      + 1
      10
      One complete database service that not only does data storage, but also search, real-time and more
      CloudBoost logo
      CloudBoost
      VS
      Datomic Cloud logo
      Datomic Cloud
      Orchestrate logo

      Orchestrate

      5
      11
      0
      5
      11
      + 1
      0
      Database as a Service. Add Search, Time-Ordered Events, Geospatial or Graph Queries Fast with a REST API
        Be the first to leave a pro
        Orchestrate logo
        Orchestrate
        VS
        Datomic Cloud logo
        Datomic Cloud
        VelocityDB logo

        VelocityDB

        1
        2
        0
        1
        2
        + 1
        0
        A NoSQL Object Database, extended as Graph Database is VelocityGraph
          Be the first to leave a pro
          VelocityDB logo
          VelocityDB
          VS
          Datomic Cloud logo
          Datomic Cloud