Jedox is a Business Intelligence and Corporate Performance Management solution. According to the vendor, their solution’s unified planning, analysis and reporting empowers decision makers from finance, sales, purchasing and marketing. Additionally, the vendor says this solution helps business users work smarter, streamline business collaboration, and make insight-based decisions with confidence. The vendor also says 1,900 organizations in 127 countries are using Jedox for real-time planning…
N/A
RabbitMQ
Score9.5 out of 10
N/A
RabbitMQ, an open source message broker, is part of Pivotal Software, a VMware company acquired in 2019, and supports message queue, multiple messaging protocols, and more.
RabbitMQ is available open source, however VMware also offers a range of commercial services for RabbitMQ; these are available as part of the Pivotal App Suite.
Best suited for financial consolidation and / or as a highly customized and compact EPM / BI solution (up to 100 CCU) with individual workflows, planning and reporting functionalities, with moderate number of users (no restrictions for any industry, all industries are covered well). It also has advanced reporting & data analysis requirements and provides an integration and reporting layer of imported data from different external systems (via ETL). It can help with migrating your legacy Excel-based business models to the Web. It is not well suited for Enterprise BI applications with expecting >500 CCU (users at the same time working with the system) - this may cause serious performance issues, as all data is kept in RAM. Jedox is also less suited for applications with heavy document management requirements (document management is not an out of the box functionality in Jedox and rather requires custom development through custom widgets etc.).
It is highly recommended that if you have microservices architecture and if you want to solve 2 phase commit issue, you should use RabbitMQ for communication between microservices. It is a quick and reliable mode of communication between microservices. It is also helpful if you want to implement a job and worker mechanism. You can push the jobs into RabbitMQ and that will be sent to the consumer. It is highly reliable so you won't miss any jobs and you can also implement a retry of jobs with the dead letter queue feature. It will be also helpful in time-consuming API. You can put time-consuming items into a queue so they will be processed later and your API will be quick.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
What RabbitMQ does well is what it's advertised to do. It is good at providing lots of high volume, high availability queue. We've seen it handle upwards of 10 million messages in its queues, spread out over 200 queues before its publish/consume rates dipped. So yeah, it can definitely handle a lot of messages and a lot of queues. Depending on the size of the machine RabbitMQ is running on, I'm sure it can handle more.
Decent number of plugins! Want a plugin that gives you an interface to view all the queues and see their publish/consume rates? Yes, there's one for that. Want a plugin to "shovel" messages from one queue to another in an emergency? Check. Want a plugin that does extra logging for all the messages received? Got you covered!
Lots of configuration possibilities. We've tuned over 100 settings over the past year to get the performance and reliability just right. This could be a downside though--it's pretty confusing and some settings were hard to understand.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Diversity. Jedox can be applied to many different use cases from small to large deployments and from budgeting to enterprise class BI solutions. But rarely is one tool able to fulfill all of these requirements in one organisation. This value proposition can be complicated for prospective users.
Awareness. Jedox punches above its weight in capability and scalability, but not enough people have heard about it and therefore procurement processes can be drawn out as a result.
It breaks communication if we don't acknowledge early. In some cases our work items are time consuming that will take a time and in that scenario we are getting errors that RabbitMQ broke the channel. It will be good if RabbitMQ provides two acknowledgements, one is for that it has been received at client side and second ack is client is completed the processing part.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
To me Jedox deserves 10/10 because it is a consistent one-in-all platform with a modern look and feel. It is intuitive to use and allows you to make intuitive applications integrating traditional business intelligence with performance management functionality. It certainly has a short learning curve, especially for those that are familiar with MS Excel. An example: I've lost count but Jedox it is available in more than 25 languages. Another: Jedox does not require programming skills... it is developed to be used by the business.
RabbitMQ is very easy to configure for all supported languages (Python, Java, etc.). I have personally used it on Raspberry Pi devices via a Flask Python API as well as in Java applications. I was able to learn it quickly and now have full mastery of it. I highly recommend it for any IoT project.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Jedox has very few bugs. Reports are available through an Excel add-in, the web and/or mobile device (IOS/Android). In my opinion, availability also means high performance, not having to wait for the system to give you the required reports, analysis, dashboards instantly.
Jedox support in general is a professional and fast responding team. An easy-to-use ticketing system is in place. Bug-related questions are solved fast (responses come usually in a few hours after the question), but some questions / tickets, that are not Jedox-related bugs (for example some advanced questions about Jedox functionality), may be forwarded to Application Management team for further processing and then it may take several days or even weeks to get a response here -> there is room for improvement here.
I gave it a 10 but we do not have a support contract with any company for RabbitMQ so there is no official support in that regard. However, there is a community and questions asked on StackOverflow or any other major question and answer site will usually get a response.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
The implementation of SSO, SAML Authentication, HTTPS, Server splitting (Frontend / Backend servers) could be more standardized and made more user friendly to set up (e.g. via setup guide). Otherwise the implementation of Jedox is quick and simple when compared to other similar technologies.
Calumo is similar product to Jedox. I have used it extensively in my previous role. It was a major contender when we evaluated a BI platform for NIDA. Calumo is a great product as well and it was a very close call. Where we found Jedox to be a better fit for NIDA was the ability to prepare dynamic reports with ease without the need to learn MDX which was used extensively by Calumo to make dynamic reports which expand or shrink based on the underlying data. Another major benefit we saw in Jedox was the whole ETL process could be managed within Jedox instead of doing it in SQL server which negates having a dedicated SQL specialist role when the scale expands.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
RabbitMQ has a few advantages over Azure Service Bus 1) RMQ handles substantially larger files - ASB tops out at 100MB, we use RabbitMQfor files over 200MB 2) RabbitMQ can be easily setup on prem - Azure Service Bus is cloud only 3) RabbitMQ exchanges are easier to configure over ASB subscriptions ASB has a few advantages too 1) Cloud based - just a few mouse clicks and you're up and running
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Scalability is often another word for speed. Given enough data, enough users or enough calculations, the tool becomes slower and slower. You will find that Jedox has a very high performance that can even be increased by the use of grafical cards. Other thaen that it does not only offer BI (looking back based on historical ERP data) but also allows you to look forward through integrated budgetting, planning, forecasting, workflow and collaboration. Not easy to find a tool that can support so much business functionality. So, also pretty scalable in that respect.
Financial budgeting and Forecasting are done in a centralized fashion in Jedox now instead of a decentralized excel based approach. A lot of cost savings and improved reliability
Easy to use self-help Dashboards and detailed reports
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Positive: we don't need to keep way too many backend machines around to deal with bursts because RabbitMQ can absorb and buffer bursts long enough to let an understaffed set of backend services to catch up on processing. Hard to put a number to it but we probably save $5k a month having fewer machines around.
Negative: we've got many angry customers due to queues suddenly disappearing and dropping our messages when we try to publish to them afterward. Ideally, RabbitMQ should warn the user when queues expire due to inactivity but it doesn't, and due to our own bugs we've lost a lot of customer data as a result.
Positive: makes decoupling the web and API services from the deeper backend services easier by providing queues as an interface. This allowed us to split up our teams and have them develop independently of each other, speeding up software development.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
