Firebase vs. Progress MarkLogic

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Firebase
Score 8.2 out of 10
N/A
Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
$0.01
Per Verification
Progress MarkLogic
Score 9.0 out of 10
N/A
MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. The vendor states it is the most secure multi-model database, and it’s deployable in any environment. They state it is an ideal database to power a data hub.
$0.01
per MCU/per hour + 0.10 per GB/per month
Pricing
FirebaseProgress MarkLogic
Editions & Modules
Phone Authentication
$0.01
Per Verification
Stored Data
$0.18
Per GiB
Low Priority Fixed
$0.01
per MCU/per hour + 0.10 per GB/per month
Standard Reserved
$0.07
per MCU/per hour + 0.10 per GB/per month
Standard On-Demand
$0.13
per MCU/per hour + 0.10 per GB/per month
Offerings
Pricing Offerings
FirebaseProgress MarkLogic
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
FirebaseProgress MarkLogic
Considered Both Products
Firebase
Chose Firebase
I actually only have experience with Firebase. It's for a good reason. It's the first database I worked with and just stuck with it. It's beginner friendly while offering advanced tool.
Chose Firebase
Firebase provides an event based data model with well defined pre-determined dimensions. Where I've seen the strength of other platforms is the user interface where data is analyzed. However, other platforms such as AEP also have advanced data cleansing and standardization …
Chose Firebase
Supabase is more user-friendly especially since it is directly integrated with Lovable, one of the most popular AI coder for non-technical users.
Chose Firebase
Supabase seems to have the best of all worlds right now. Followed by MongoDB/Firebase for smaller projects requiring less manpower and resources. Azure and Microsoft are reserved for existing projects and larger corporate clients.
Chose Firebase
Although there are other backend platforms that could have provided us with a solution to our project. The way of grouping the solution in FIREBASE, atomizing in the same project the database, cloud functions, authentication, push notifications, etc., has given us a clearer …
Chose Firebase
Unlike other tools in the GCP suite that have an equivalent in other clouds such as Bigquery (Athenas on AWS), AI Platform (Sagemaker), Storage (S3), we do not find an equivalent as complete as Firebase in any other provider. This is the main reason why we chose this provider …
Chose Firebase
Firebase came to a multiuse case for our product for authenticating backend services, users on the app & get data on the user base using the dashboard.
Chose Firebase
Firebase has a single NoSQL database, it is a simple, powerful and uniform application development platform in connectors, it has multiple programming languages ​​such as JavaScript and necessary tools that will simplify the creation of applications.
Chose Firebase
Firebase poses great documentation and integration with Android devices. And it's very good as well for iOS ones. So, for these scenarios, Firebase becomes the ideal ally.
Chose Firebase
It eases the app development process, has an extensive database that allows you to store media files in the cloud, supports robust uploads and downloads, and login authentication on any platform.
Chose Firebase
PostgreSQL is a relational database and is well suited for complex applications, however, Firebase is well suited for light and faster applications.
Chose Firebase
Firebase is easy to manage and scale really well for web application services. It offers better authentication and is easy to implement. For real-time analytics on web applications, it works very well. Firebase offers more features compared to other services especially it can …
Chose Firebase
  • User interface and console are very easy to understand
  • There is no pain in Integration with IOS, Android, and unity platforms
  • Cost-effective
Chose Firebase
We choose Firebase for various reasons:
  • A large set of resources and world-class Google support.
  • Pricing was a larger role in this decision.
Chose Firebase
If I get a suitable budget next year, I'll be switching us to Adobe Analytics. Their app/web tracking and the interface are streets ahead of Firebase.
Chose Firebase
Firebase is a much more comprehensive tool. While Fabric only had user traffic and trends data, it did not have the user communication set of tools. While CleverTap has CRM tools, it does not have tools for developers and product teams. While Adobe Analytics is good with …
Chose Firebase
I haven't played much with Heroku beyond deploying projects from Github. It looks to be very similar in providing a cloud-based platform for developing and deploying web apps as quickly as possible. I would look at comparing both of these before choosing a solution. I am just …
Chose Firebase
We chose Firebase for the following reasons.
  • Online resources.
  • Comes with better support.
Chose Firebase
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted …
Chose Firebase
Firebase does a lot of things well, but Branch.io does a lot of things great. We originally chose Firebase because it was free, had great crash reporting, and full event tracking. As we began to scale, increase paid marketing spend, and implement features such as journey …
Chose Firebase
It's tough to pick out competitors against Firebase as I'm really unsure and doubt there's another product exactly like it. As mentioned before Firebase literally does everything you can imagine for a mobile application but doesn't get insanely deep in one feature or action. It …
Chose Firebase
Firebase is well suited for projects with simpler database workloads that require its real-time features. For data that is heavily read in real time, it's a great choice and gives developers a lot of features that would have been complicated and time-consuming to build up front …
Progress MarkLogic
Chose Progress MarkLogic
In comparison to both Mongo and HBase, MarkLogic wins in terms of integration to other systems, while loosing in terms of pricing.
In terms of documentation all will be in same range putting MarkLogic a bit forward.
Chose Progress MarkLogic
MarkLogic is good at what it does: storing and searching XML with a REST interface. The amount of support out there for the other NoSQL products is what gives them the best advantage. Many plugins exist for those, none exist for MarkLogic. Even the proprietary ones like …
Chose Progress MarkLogic
There's no other single product that directly compares to all the features that are packed into MarkLogic. Generally speaking, you're looking at a combination of many products to build a stack that competes feature-for-feature. Even if you're leveraging only a limited set of …
Chose Progress MarkLogic
I have used most of the common RDBMS databases (SQL Server, Oracle, MySQL, etc.). MarkLogic is more dependable, faster, and flexible. I would not willingly go back to RDBMS. As far as open source competition to MarkLogic such as MongoDB, I haven't used it myself so I don't have …
Chose Progress MarkLogic
We had Fast in place when Microsoft had bought it up and was going to change / deprecate it. One of the biggest advantages of MarkLogic for search actually had to do with the rest of the content pipeline - it allowed us to have it all in one technology. On the NoSQL side, we …
Features
FirebaseProgress MarkLogic
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Firebase
-
Ratings
Progress MarkLogic
7.9
Ratings
8% below category average
Performance00 Ratings8.50 Ratings
Availability00 Ratings8.00 Ratings
Concurrency00 Ratings7.50 Ratings
Security00 Ratings9.00 Ratings
Scalability00 Ratings8.50 Ratings
Data model flexibility00 Ratings7.00 Ratings
Deployment model flexibility00 Ratings6.50 Ratings
Best Alternatives
FirebaseProgress MarkLogic
Small Businesses
AWS Lambda
AWS Lambda
Score 8.2 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
FirebaseProgress MarkLogic
Likelihood to Recommend
7.3
(0 ratings)
9.0
(0 ratings)
Likelihood to Renew
-
(0 ratings)
7.0
(0 ratings)
Usability
7.0
(0 ratings)
9.0
(0 ratings)
Support Rating
7.3
(0 ratings)
9.0
(0 ratings)
User Testimonials
FirebaseProgress MarkLogic
Likelihood to Recommend
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
Read full review
In an area where it will be built once and maintained, it shines. If you aim to use CI, temporary environments, or anything else, it is not very effective. Licensing is almost impossible on boxes that are to be created on the fly.
Read full review
Pros
  • Extremely robust. Has about any tool you can think of under one roof making it extremely useful as a backup platform for data analytics or small teams that need something quickly.
  • Intuitive and easy UI/UX. Being made and owned by Google, you expect nothing less. Very easy to use for anyone that has any marketing or analytical experience especially in Google Analytics (which I just assume all marketers do).
  • Safe, secure, and sturdy. Never need to worry about downtimes or misinformation as it's as clean and safe as it is being run by Google.
  • FREE! What else is there to say. Unless you're an extremely large application handling hundreds of thousands to millions of users, this pay as you go plan will stay free.
Read full review
  • Indexing is a major strength of MarkLogic. The out-of-the-box configuration is set up to handle a combination of text and fielded data. The indexing is also highly configurable. Those configuration options are at the heart of a lot of our high-volume, high-performance applications.
  • The industrial strength transactions and security are also a strength, particularly when we are dealing with user-created intellectual property.
  • The engineering support is a strength. They are big enough to have a really strong support and engineering staff, but small enough so that a medium-sized customer has access to it. They are very responsive to questions and problem reports.
  • The ability to move easily among XML and JSON is a strength.
Read full review
Cons
  • Firebase/Firestore has very limited support for querying more complicated items; for example, performing a simple string search is not possible.
  • While upfront costs are low, costs can grow quickly if you're not careful about what you are being billed for.
  • Dashboards have at times shown different information to what is billed, and support from Google is less than stellar and not as effective as that from Amazon or Microsoft.
Read full review
  • How to do complete data profiling on documents loaded in Marklogic database?
  • Customers need a tools which can be customized to suit their data profiling needs but currently the tools which MarkLogic provides fall short on this requirement.
  • Unit testing framework which is using only XQuery as the language is lacking some features.
Read full review
Likelihood to Renew
No answers on this topic
Our firm has consultants for a number of technologies/disciplines. While I am capable and experienced in other areas, my preference is always to work on engagements with MarkLogic. As an architect and developer, I get far more flexibility and performance from one product instead of cobbling together a stack of several products to provide a capability that MarkLogic has rolled into one great product.
Read full review
Usability
I don't use the Firebase UI much, but rather connect it to GA4. GA4 has a great event model but the GA4 UI and analysis capabilities are limited. It's harder to measure product usage type of engagement but if you have the time and resources to leverage the GA4 to BiqQuery export you'll have all the raw event data you'll need for deep analysis, segmentation, and audience activation.
Read full review
Very little about it can be done better or with greater ease. Even things that seem difficult aren't really that bad. There's multiple ways to accomplish any admin task. MarkLogic requires a fraction of administrative effort that you see with enterprise RDBMS like Oracle. MarkLogic is continually improving the tools to simplify cluster configuration and maintenance.
Read full review
Support Rating
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
Read full review
There's always room for improvement. Some problems get solved faster than others, of course. MarkLogic's direct support is very responsive and professional. If they can't help immediately, they always have good feedback and are eager to receive information and details to work to replicate the problem. They are quick to escalate major support issues and production show-stopping problems. In addition to MarkLogic's direct support, there are several employees who are very active among the community and many questions and common issues get quick attention from helpful responses to email and StackOverflow questions.
Read full review
Alternatives Considered
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
Read full review
In comparison to both Mongo and HBase, MarkLogic wins in terms of integration to other systems, while loosing in terms of pricing. In terms of documentation all will be in same range putting MarkLogic a bit forward.
Read full review
Return on Investment
  • Firebase has been able to help us understand reliably, the drop-off in our user flows with their funnel feature. This has made it easy for us to be able to pinpoint weaknesses in our funnel and test and optimize with data as the dependent variable.
  • From an economic standpoint, we don't pay for Firebase which is great, but as the saying goes "You get what you pay for" also holds true in this context. As we looked to grow and scale, we looked for a paid solution.
  • From a developer resource standpoint, Firebase has been extremely easy to integrate into our app. Whether it be the event tracking, dynamic links or crash reporting we have not had to waste too much developer time thanks to their well-organized developer docs.
Read full review
  • It took longer than expected to develop our application and get the level of consistent performance necessary. As a result, profit was flat for a couple of years but the benefits are really starting to kick in.
Read full review
ScreenShots