What is Realm and what are its top alternatives?
Top Alternatives to Realm
Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...
SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file. ...
It is a library allowing to save the redux store in the local storage of your browser. It promises to retain the users’ redux-state which is an attractive proposition for most developers. ...
Realm React Native
It is an open source Android ORM making development for SQLite databases fun again. It relieves developers from dealing with low-level database requirements while saving development time. ...
It is for developers who look for performance and ease of use. We are committed to providing you with the easiest APIs for you to keep your code short and maintainable. No SQL under the hood-Simply faster. Unlike other databases, it has been built from the ground up using key-value storage instead of column storage. The resulting performance is 10x faster than the leading alternative, we welcome you to try it yourself. It is fast regardless of the amount of data or operating system you are using. ...
Realm alternatives & related posts
- Realtime backend made easy357
- Fast and responsive261
- Easy setup233
- Backed by google120
- Angular adaptor80
- Great customer support36
- Great documentation25
- Real-time synchronization22
- Mobile friendly19
- Rapid prototyping17
- Great security12
- Automatic scaling10
- Freakingly awesome9
- Super fast development8
- Angularfire is an amazing addition!8
- Awesome next-gen backend6
- Ios adaptor6
- Firebase hosting5
- Built in user auth/oauth5
- Very easy to use4
- Brilliant for startups3
- It's made development super fast3
- Low battery consumption2
- The concurrent updates create a great experience2
- I can quickly create static web apps with no backend2
- Great all-round functionality2
- Speed of light2
- Easy to use1
- Good Free Limits1
- JS Offline and Sync suport1
- Easy Reactjs integration1
- Faster workflow1
- Push notification1
- Can become expensive25
- No open source, you depend on external company14
- Scalability is not infinite14
- Not Flexible Enough9
- Cant filter queries5
- Very unstable server3
- Too many errors2
- No Relational Data2
related Firebase posts
This is my stack in Application & Data
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.
- Preinstalled on iOS and Android28
- Tcl integration1
- Portable A database on my USB 'love it'1
- Not for multi-process of multithreaded apps2
- Needs different binaries for each platform1
related SQLite posts
I need to add a DBMS to my stack, but I don't know which. I'm tempted to learn SQLite since it would be useful to me with its focus on local access without concurrency. However, doing so feels like I would be defeating the purpose of trying to expand my skill set since it seems like most enterprise applications have the opposite requirements.
To be able to apply what I learn to more projects, what should I try to learn? MySQL? PostgreSQL? Something else? Is there a comfortable middle ground between high applicability and ease of use?
SQLite is a tricky beast. It's great if you're working single-threaded, but a Terrible Idea if you've got more than one concurrent connection. You use it because it's easy to setup, light, and portable (it's just a file).
In Paperless, we've built a self-hosted web application, so it makes sense to standardise on something small & light, and as we don't have to worry about multiple connections (it's just you using the app), it's a perfect fit.
For users wanting to scale Paperless up to a multi-user environment though, we do provide the hooks to switch to PostgreSQL .
related Redux Persist posts
- Reactive Database1