Google offers Cloud Pub/Sub, a managed message oriented middleware supporting many-to-many asynchronous messaging between applications.
N/A
RabbitMQ
Score 9.1 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.
N/A
Agentforce Sales
Score 8.7 out of 10
N/A
Salesforce' Agentforce Sales (formerly Salesforce Sales Cloud) is the company's flagship CRM platform. The AI CRM for Sales features data built right in.
We considered several messaging platforms including Kafka and Kinesis but both would have required more developer work and didn't integrate as nicely with our ecosystem. RabbitMQ is another messaging platform I've researched and prototyped on; it also would have required more …
Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution. Since we are not using …
If you want to stream high volumes of data, be it for ETL streaming or event sourcing, Google Cloud Pub/Sub is your go-to tool. It's easy to learn, easy to observe its metrics and scales with ease without additional configuration so if you have more producers of consumers, all you need to do is to deploy on k8s your solutions so that you can perform autoscaling on your pods to adjust to the data volume. The DLQ is also very transparent and easy to configure. Your code will have no logic whatsoever regarding orchestrating pubsub, you just plug and play. However, if you are not in the Google Cloud Pub/Sub environment, you might have trouble or be most likely unable to use it since I think it's a product of Google Cloud.
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.
Obviously, for any business, there are two main areas to focus on — the sales path and the service path. Sales Cloud wouldn’t be suited for a company that’s primarily into support services. For those kinds of companies, Salesforce has a different product — Service Cloud. So, for anyone in the support or service space, Sales Cloud isn’t the right fit.
With a pub/sub architecture the consumer is decoupled in time from the publisher i.e. if the consumer goes down, it can replay any events that occurred during its downtime.
It also allows consumer to throttle and batch incoming data providing much needed flexibility while working with multiple types of data sources
A simple and easy to use UI on cloud console for setup and debugging
It enables event-driven architectures and asynchronous parallel processing, while improving performance, reliability and scalability
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.
The customizations - We have an organization that operates differently from most companies, so we’ve had to implement quite a few customizations — and Salesforce allows us to do that quite quickly. Most of the time, delays come from dependencies on other internal parties rather than the system itself.
From my perspective as a consultant, one of the biggest advantages is that everything is in Salesforce — all the details, all in one place. The ability to customize it easily is a big plus; there’s really a lot you can do with it.
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.
We still need to include the production part. We started using Salesforce to sell the seeds — our inventory is in SAP — and from there we handle sales and track the process of planting, harvesting, selling, and then collecting payments. But we don’t yet manage the earlier production processes, like production planning. We handle allocation, but not full production planning, and that’s an area where we still have room for improvement.
It serves all of our purposes in the most transparent way I can imagine, after seeing other message queueing providers, I can only attest to its quality.
There are days when I wish we hadn't switched, but I know that if we put in the time, we will get to where we want to be with the software and that it has many more capabilities than anything else we looked at. However, the amount of time and onboarding we need to do is also far greater than we realized/were told when we originally bought the product. They told us we should hire onboarding support, but at the end, after we had already reached our budget maximum for this, so it's been slower than we had hoped.
It is easy to create Google Cloud Pub/Sub topics from both Web Console and CLI commands.
Google Cloud Pub/Sub supports creation of one or more subscriptions.
By supporting a BigQuery Pub/Sub subscription to automatically write to a BigQuery table it simplifies development by avoiding implementation of a custom micro service for writes to BigQuery.
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.
Because I think it could be easier. We have different standards today since we’re used to interacting with consumer apps like Starbucks, where all you do is scan your card. Then, when you use Sales Cloud, there are still a lot of manual inputs. So my mission with AI is really about figuring out how to make that easier.
Salesforce is always available securely from any internet-capable device anywhere in the world, UNLESS you choose to set security measures so that ONLY trusted IP ranges may access the system at certain times of the day. It's all about choice and flexibility with Salesforce products.
Salesforce performance in general is excellent. "The cloud infrastructure beneath Force.com has been fine-tuned over the past 10 years. It powers nearly 100,000+ businesses running more than 185,000 applications that 3 million users count on every day." Points per Salesforce - 1) Multitenant kernel - With a multitenant platform, each business that uses the app doesn’t have its own copy. Instead, all businesses share a single copy and then customize it for their specific needs. 2) ISO 27001 certified security - You can’t compromise when it comes to enterprise-level security. Force.com is road-tested and trusted by nearly 100,000+ companies, including many of the world’s most security-conscious organizations, such as banks and health care providers. 3) Proven reliability - All Force.com apps run on world-class data centers with backup, failover, and disaster-recovery facilities. Force.com has had a proven 99.9 percent uptime record for years. 4) Proven, real-time scalability - Force.com is used by many of the world's largest enterprises, including Cisco, Japan Post Network, and Symantec. Applications can automatically scale from a few users to millions of page views, as needed. 5) Real-time query optimizer - You need fast access to your data. The Force.com query optimizer delivers under 300ms response time, at a massive scale. 6) Real-time transparent system status - You can always see real-time system performance, availability, and security information at trust.salesforce.com. 7) Real-time upgrades - Unlike traditional software platforms, our upgrades never break your customizations, code, or integrations. We upgrade the platform for you 3 to 4 times each year. As a result, you’re always on the latest version, with access to the latest features, performance, and security enhancements. 8) Real-time sandbox environments - With a single click, you can create copies of your applications, configuration, and data in separate environments for development, testing, and training. 9) Three global production data centers and disaster recovery - Force.com runs on three geographically dispersed, mirrored data centers with built-in replication, disaster recovery, a redundant network backbone, and no single points of failure
They have decent documentation, but you need to pay for support. We weren't able to answer all our questions with the documentation and didn't have time to setup support before we needed it so I can't give it a higher rating but I think it tends to be a bit slow unless you're a GCP enterprise support customer.
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.
The overall support has been good. More and more features are being released quite frequently. Very small features are also making big difference in how the tool can be adapted and used better. If there is anything we need or are stuck, the support team sets up a call and helps in resolving the issue/provides workarounds.
I attended two training sessions. I would rate them a 4 as an advanced user. It was very basic – great for someone new – would give 8+ for new person.
I had 3 years of experience at the time. I skipped basic and went onto advanced and still not helpful. A lot of it was best practices that didn’t feel relevant for our business
I have gone through multiple. The content that’s delivered is quite basic – I wish they had more advanced training.
We are grandfathered into premium support plus training. We get unlimited access to instructor led and online training for free. We have taken advantage of this
Just from an organizational standpoint - we standardized our data prior to moving to Salesforce. But we essentially standardized it wrong. That's created a big disgusting mess for us know that I'll have to deal with as the Admin. Be sure you think through use cases prior to doing something like that - seek outside opinions on how the data will work best, especially depending on what else you're going to integrate with Salesforce.
Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution. Since we are not using GCP only for Pub/Sub the choice depends on other variables.
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
So I've evaluated, implemented Microsoft Dynamics in the past. I've used Oracle CRM solutions. I've used Daylight, which is a very niche CRM system the last couple of years. And I've evaluated a variety from Legacy Microsoft Ones to Zoho and Sugar when making implementation decisions at other companies. But usually I've gone with Salesforce. I'd say it's better than most. The only one that I generally prefer, and last time I chose an implementation from scratch, I did Microsoft Dynamics. And the reason is for small mid-size organization, Microsoft Dynamics, if you already have Microsoft Office products, it's much better integrated to all of the Excel, Word, OneNote, Outlook email than what you get from Salesforce. And so that's the only one that if someone's a Microsoft organization and small sized company, it'll save a lot of integration things, a lot of security, a lot of login and access and IT management by just sticking within the Microsoft ecosystem. But outside of that, if you don't use Microsoft or if you're a large organization or have other needs that you want, Salesforce I'd say is better than all of the other CRM offerings out there. It's the easiest to use and the most robust and the most vendors and products for the ecosystem.
Salesforce is the most widely used CRM system. Professionalism tends to increase when things go wrong for market leaders. Salesforce considers us as users because they own the market. Having all of our data in one place and all of our teams working within Salesforce. Anyone who uses Salesforce is impacted by it, even if they don't.
You can just plug in consumers at will and it will respond, there's no need for further configuration or introducing new concepts. You have a queue, if it's slow, you plug in more consumers to process more messages: simple as that.
It's very scalable as it has a ton of features (but you do need an admin who understands how to leverage these features). Because of the various features, we've also needed to host onboarding sessions with our users so that they can familiarize themselves with the platform, which isn't always super user-friendly or intuitive.
Using Salesforce.com has made my daily routines more efficient and simplified the manual tasks I had to perform independently. I can now access data from any device, online or offline, and provide better guidance to my team about the forecasts provided by the built-in artificial intelligence (AI). A chat with a Salesforce support specialist would be great. The knowledge base has a community forum where Salesforce users can ask questions and learn more about the product.
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.
It allows me to keep a close eye on all of my performance metrics through the Dashboard Reporting, ie what my sales pipeline looks like, how much it's changed in the last 60 days, new opportunities created in the last 7 days, # of emails sent for the week, etc. The ease of the design and output make it really easy to check my progress throughout the day to find where I have holes and am falling short on my personal and work goals. It's resulted in greater transparency with my Mgmt Team and shorter 1-on-1 mtgs with my boss as he can see exactly where I am at all times (to be fair, I'm a senior sales rep, so he pretty much lets me do my job completely unfettered), but it does prove that I am continually producing which recently resulted in a raise I didn't even ask for.
The SF repository is so detailed that I don't have to spend tons of time finding frequently used websites attached to a client or see what all interactions with the company look like. Even though I don't use SF for my bulk emails and email sequences, SF provides me with an email to use in the bcc of these emails which links everything back to SF. I find that extremely helpful. This really impacts my efficiency and I can honestly say that once I started using all the functionality of data management, it saved me about 20% of my time/week that I could then allocate towards other revenue-generating tasks like prospecting and account management. The more time I have for those, the better. My year-over-year on accounts 1 year and older just grew by 17% this last year.
