Parse server vs Sendbird
This Parse server vs Sendbird comparison was created based on reviews from developers and our best attempts to perform analysis by looking at documentation and other publicly available resources.
Easily build complete, trusted realtime functionality.
Take our APIs for a spinParse server | Sendbird | |
---|---|---|
Getting started and developer experience | ||
Time to "hello world" Reviewed by 3+ independent developers Ratings were given based on the average amount of time it takes to sign up to a new account and publish the first message. | 5 / 5 5 = <30 min | 4 / 5 5 = <30 min |
Demos / Tutorials A selection of online demos and tutorials so you can test and see the code in action. Explore Ably's tutorials for our pub/sub messaging platform | ||
Documentation Reviewed by 3+ independent developers Explore Ably's documentation for our pub/sub messaging platform | 4.33 / 5 Getting started guides / 5 Information architecture and developer journey / 5 API reference documentation / 5 Readability, design and navigation / 5 Quality of code / 5 Breadth and quality of tutorials / 5 P: “Documentation is detailed, with many examples and tutorials from how to set up the parse server, connect clients to it, using different databases and hosting on different platforms”. O: “The documentation is extensive and at the same time offers higher level explanations for the more detailed sections.” W: “While the documentation offers a lot of information, examples and tutorials it could have been organized in a more clear manner and made more readable.” | 4.33 / 5 Getting started guides / 5 Information architecture and developer journey / 5 API reference documentation / 5 Readability, design and navigation / 5 Quality of code / 5 Breadth and quality of tutorials / 5 The documentation is comprehensive, detailed, and clear, with sample projects. It's easily navigable, and the written and video tutorials are in-depth, but there could be more of them. The different products that make up the Sendbird platform are clearly separated (e.g. Chat, Calls, UIKit, etc) before introducing the SDKs and API. This gives users an overview of the products before diving into its documentation. Each product has API reference documentation. The key functionalities of that product are listed out for easy access. Generally, in terms of comprehensiveness, readability, navigation, ease of use, and code quality, the documentation is very solid. |
Dashboard or dev console Reviewed by 3+ independent developers Sign up for free and explore Ably's pub/sub messaging platform | 4 / 5 Ease of use / 5 Stats and reports / 5 Functionality / 5 P: “The dashboard is easy to set up. You get a good overview of the stored data, so you can easily manage the database. Features such as webhooks, jobs, logs, API console and push notifications are easily accessible. Lack of performance metrics is a downside.” O: “The dashboard has a clean and simple UI with management sections for the webhooks, jobs, logs, configs and API console. It also includes a browsing view.” W: “The dashboard UI is easy to understand and self-explanatory. On the downside there is no informative metrics available but on the upside there is a lot of functionality and configurations options and the API console where you can send HTTP and GraphQL queries is a nice feature.” | 5 / 5 Ease of use / 5 Stats and reports / 5 Functionality / 5 The dashboard allows you to create and manage applications. It also enables you to see all the stats and reports you need about monthly and daily active users, and peak concurrent connections. It also enables you to create and manage chat channels and make calls, making it easy to test. It has a slick design and is quite intuitive to use, and it’s divided into five features; overview, users, settings, calls, chat. It also has moderation tools that you can use to protect your conversations directly from your dashboard. |
SDKs Note: Only official SDKs were taken into account. Explore Ably's 25+ SDKs for our pub/sub messaging platform | 13 SDKs Including:
| 5 SDKs Including:
|
API structure Reviewed by 3+ independent developers | 4.50 / 5 API consistency across SDKs / 5 Well structured / 5 Intuitive / 5 Simple / 5 P: "The API across SDKs are mostly consistent, but support for Pub/sub is not available on all SDKs. Plenty of code examples of how to perform various operations”. O: “Most SDKs are well structured, simple and consistent. Although some are missing an API reference.” W: “The SDKs are intuitive and well structured for the most part. The SDKs could however have been more consistent.” | 5 / 5 API consistency across SDKs / 5 Well structured / 5 Intuitive / 5 Simple / 5 The API is pretty straightforward, consistent across SDKs, it’s also intuitive and easy to use provided you read the documentation. I found it easy to figure out what to do without a lot of help. I find the methods simple, easy to remember and easy to understand. |
Parse server | Sendbird |
---|---|
"Hello world" code example | |
|
|
Parse server | Sendbird | |
---|---|---|
Realtime features | ||
Pub/Sub messaging Pub/Sub is a design pattern that lets any number of publishers (producers) push messages to channels (also known as topics). Multiple subscribers (consumers) can subscribe to a channel to consume published messages. Explore Ably's pub/sub messaging implementation | Limited There is support for pub/sub messaging using LiveQueries in the Javascript SDK, which uses WebSockets to subscribe & publish to channels. But LiveQueries is limited to the Javascript SDK. | |
Message queues A message queue is a form of asynchronous service-to-service communication. Messages are stored on a queue until they are processed. Note that each message is only consumed by one subscriber (consumer). Explore Ably's message queues implementation | ||
Presence Presence enables you to track the online and offline status of devices and end-users in real time and to store their state. Essential for chat apps and multiplayer games. Explore Ably's presence implementation | Limited One could keep track of online clients by using the LiveQuery triggers to know whether or not a client is connected. But there is no built functionality for this. | Limited Presence is only available for Sendbird Chat, but it's not supported by other products like Sendbird Desk and Sendbird Calls. |
Message history Message history provides a means to retrieve previously published messages. For this to be possible, message data must be stored (persisted) somewhere. Explore Ably's message history implementation | ||
Connection state recovery (stream resume) In the case of unreliable network conditions, clients may suddenly disconnect.Connection state recovery ensures that when they reconnect, the data stream resumes exactly where it left off. Explore Ably' s connection state recovery implementation | ||
Guaranteed message ordering Ordering ensures that messages are delivered to consumers in the same order that producers publish them. Explore Ably' s guaranteed message ordering implementation | ||
Exactly-once semantics Exactly-once is a system-wide data integrity guarantee that ensures each message is delivered to consumers exactly-once. Explore Ably' s idempotent publishing implementation | Limited Idempodency enforcement exists, as an experimental feature that may not be appropriate for production. | |
Message delta compression Message delta compression enables you to only send the changes from the previous message to subscribers each time there’s an update, instead of the entire message. Useful for use cases where there is a significant degree of similarity between successive messages. Explore Ably' s message delta compression implementation | ||
Native push notifications Native push notifications can be used to deliver messages even when clients are offline. Useful for geolocation updates or news alerts. Explore Ably's push notifications implementation | ||
Webhooks Webhooks provide a mechanism to get messages and other types of events (such as clients entering or leaving channels) pushed to your servers over HTTP. Explore Ably's webhooks implementation | ||
Serverless functions A serverless function is essentially an isolated, single-purpose piece of code that is only executed when it’ triggered by an event. For example, you can use serverless functions to send a welcome message to clients when they become present on chat channels. Note that serverless functions are usually fully managed by cloud vendors. Explore Ably's serverless functions implementation | Limited Cloud functions are used in parse server to run single-prupose piece of code. But is up to you to host the parse server, where the cloud functions are invoked from. The pricing model is different, since you are hosting the parse server yourself, you can invoke the cloud function for as many times as you like. Services like AWS Lambda charges you for the number of requests made and the duration of those requests. | |
Built-in integrations Which popular services & systems are Parse server and Sendbird integrated with? Explore Ably's library of integrations | Webhooks
Serverless functions
Streaming
| Webhooks
Serverless functions
Streaming
|
Known limits and constraints Find out practical limits, such as the maximum message size, or the maximum number of concurrent connections. Explore the practical limits of the Ably pub/sub messaging platform | Publisher throughput N/A Maximum message size N/A Maximum number of topics N/A Maximum number of connections N/A | Publisher throughput Unknown Maximum message size Unknown Maximum number of topics Unknown Maximum number of connections Unknown |
Supported development platforms, languages, open protocols and cloud models | ||
---|---|---|
Development platforms & operating systems Which popular development platforms and operating systems do Parse server and Sendbird support via official SDKs? Explore the development platforms supported by Ably |
|
|
Languages Which popular programming languages do Parse server and Sendbird support via offical SDKs? Explore the programming languages supported by Ably |
|
|
Open protocols Which popular open protocols do Parse server and Sendbird support? Explore the open protocols supported by Ably |
|
|
Cloud models Which popular cloud models do Parse server and Sendbird support? |
|
|
Global and reliable edge service | ||
---|---|---|
Edge messaging network with latency-based routing Latency-based routing ensures that clients are always routed to the nearest datacenter and point of presence. Explore Ably's routing mechanism that mitigates network and DNS issues | N/A | |
Multi-region data replication (message durability) Multi-region data replication (storage) protects against single points of failure and ensures message data durability. Learn how Ably ensures message durability | N/A | |
Uptime SLAs Here’s what the most common SLAs amount to in terms of downtime over a calendar year: 99.999% SLA = 5m 15s downtime per year 99.99% SLA = 52m 35s downtime per year 99.95% SLA = 4h 22m 58s downtime per year 99.9% SLA = 8h 45m 56s downtime per year 99% SLA = 3d 15h 39m 29s downtime per year Source: https://uptime.is/ | N/A | Unknown |
Quality of Service What QoS guarantees do Parse server and Sendbird provide natively? Explore Ably's availability and uptime guarantees for our pub/sub messaging platform |
|
|
Security | ||
---|---|---|
API key authentication The simplest way to authenticate. Involves using private API keys that you can usually create and edit via a dashboard. Recommended to be used server-side, as private API keys shouldn’t be shared with untrusted parties. Explore Ably's implementation of API key authentication | ||
Token-based authentication Which popular token-based authentication mechanisms do Parse server and Sendbird support? Note that token-based authentication is usually the recommended strategy on the client-side as it provides more fine-grained access control and limits the risk of credentials being compromised. Explore Ably's implementation of token-based authentication |
|
|
Configurable rules and permissions Which types of configurable rules and permissions do Parse server and Sendbird support? Explore Ably's configurable rules and permissions |
|
|
Message encryption Which types of message encryption do Parse server and Sendbird support? Explore Ably's message encryption mechanisms |
|
|
Formal certifications Which formal certifications are Parse server and Sendbird compliant with? Explore Ably's security and compliance for our pub/sub messaging platform |
|
|
Pricing & Support | ||
---|---|---|
Free package What do the free packages offered by Parse server and Sendbird consist of? Explore Ably's free package for our pub/sub messaging platform | N/A | No free package |
Pricing model How are the Parse server and Sendbird pricing models calculated? Explore Ably's pricing model for our pub/sub messaging platform | N/A | Pricing is divided into two categories: Sendbird Chat and Sendbird Calls. Sendbird Chat is $399/month |
Enterprise package What benefits do the Parse server and Sendbird enterprise packages offer? Explore Ably's enterprise package for our pub/sub messaging platform | N/A | Sendbird offers a Premium Support package called Sendbird Desk. You’ll need to fill out a form to get started. |
Community Reviewed by 3+ independent developers Explore Ably's community support channel for our pub/sub messaging platform | 4 / 5 Presence on multiple channels / 5 Size and activity / 5 P: “Parse platform has 18k stars on github and 18k questions on Stack Overflow. It’s safe to say there is a solid community. There exist plenty of SDKs developed by the community.” O: “Parse platform has an extensive community with a lot of activity on both Github and StackOverflow, it also has a presence on Twitter.” W: “Parse has an active community with 18k stars on GitHub and there is also a substantial amount of questions about Parse Server on StackOverflow. There is a gitter for ParsePlatform but it doesn't seem quite as active.” | 3 / 5 Presence on multiple channels / 5 Size and activity / 5 Sendbird has tiny but growing community presence on a few channels such as StackOverflow (less active) and their website (more active), with a fair number of users and engagement (but a small number of tutorials). Stackoverflow has some answered questions. |
Support What types of support options and response times do Parse server and Sendbird offer? Explore Ably's support options for our pub/sub messaging platform | N/A | General support options Email, support ticket, technical documentation, community support (e.g. forums or Stack Overflow). Enterprise support Sendbird offers an enterprise package, which includes 24/7 phone, email, and chat access via Slack (with extra payment), access to customer success manager and quarterly business review Response time < 24 hours for general guidance queries < 3 hours for key functionality impaired in production(only applies to L1, L2 and L3). |
Disclaimer: The information presented for Parse server was last updated on 28 February 2021 and on 28 February 2021 for Sendbird. It is possible that some details may now be out of date. If you think that’s the case, please let us know so we can update them. In any case, you should not rely solely on the information presented here and must check with each provider before deciding to integrate or buy any of these two solutions.
View more comparisons
More to explore
About Ably
Ably is an enterprise-ready pub/sub messaging platform. We make it easy to efficiently design, quickly ship, and seamlessly scale critical realtime functionality delivered directly to end-users. Everyday we deliver billions of realtime messages to millions of users for thousands of companies.
Compare packages
Documentation
Rapidly build production-ready realtime capabilities with quickstart guides, realtime concepts, and full API reference.
Read the docs
Compare our tech
View more comparisons between Ably and other realtime messaging solutions and see why we are clearly the better choice.
View all comparisons