Mule ESB vs. Springbot

If you’re bringing anything into Salesforce you should just invest now into Mule, you will get your money’s worth and find a myriad of uses to build APIs between many other systems. Once you build a component you can easily reuse it as a building block to attach to another source/destination. This makes it easy to ramp up quickly and spread usage of Mule throughout your enterprise. A good value for medium to large companies, but probably cheaper to outsource your job to a consulting firm if you are smaller.

Incentivized

Well Suited For:

• Small businesses with small marketing teams.
• Shopify Customers.
• Small businesses that want more reporting/segmented lists.
• Businesses that are upgrading from a service like Constant Contact or Mailchimp.

Less appropriate

• Customer who are currently using Klaviyo.
• Business who do not have a Shopify website.

• It is best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
• Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
• Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
• Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.

Incentivized

• The demographic data was great. I could see how many males vs. females, ages, income, married, with or without children. It gave me a good idea of who my customers were.
• Using their tracking URLs in all of our campaigns allowed us to get a better idea of what exactly was driving revenue.
• Not only could I see top performing products, which I can do within Magento, I could also see top selling categories and colors.
• I can pull a Coupon Usage report our of Magento, but Springbot gave me additional info like AOV and ROI on those codes.
• Springbot also gave me a lot of info about our abandoned carts. It shows us which products are most abandoned along with views, conversion rates, etc.
• Springbot gave us an Instagram Shop page that allowed us to curate social shares and then tie them to products on our site.

Incentivized

• Make sure to not over-engineer shared components. It can complicate development
• Create a roadmap for where you are going - if not, you may miss components
• I suggest getting support, otherwise it could be a difficult learning curve

Incentivized

• After our purchase, I let spring or know that I was currently too busy to implement the system and to put things on hold. They ignored this request and kept charging us a monthly fee without using any of their systems. I have only logged in once. Nothing has been set up. They can see that from their side.
• After multiple emails back and forth their out was in the user agreement. I never asked for my money back only credit so I can regroup and when I have time get on to implant the systems. They tell me they don't do that.
• They don't care about any of the customer's needs. They only care about charging you that monthly fee. Terrible bus plan. With enough bad feedback, they will suffer from such a narrow plan.
• I wish we had actual information about the cons using the system. Unfortunately I was not given the opportunity to do unless I wanted to keep paying while not using the system.

Springbot has top navigation that helps me quickly jump from emails to social, and reporting very easily.

We have raved about Springbot's support because they always get back with us so quickly. Our rep, Jared has been phenomenal in helping us, always being available to chat with us and explaining some of the metrics with us so we can better understand. He completely handles our ads, checks on them, and lets us know when to update and why.

It doesn't have API . We have to go for another API manager. But in Mule, it has both API manager and ESB

Incentivized

Springbit is more expensive, more complicated and delivered less.

• Overall a great tool for complex integrations

Incentivized

• Springbot gave us a better idea of who our customer was. We just launched in January 2015 having been B2B previously. So we weren't really sure who we were marketing to.
• I only paid $200/month for the service so I didn't waste a ton of money trying it out. They have a 30 day cancellation policy so I wasn't stuck in a year long contract.
• It was a let down because I had such high hopes of everything it would allow me to do and see with one platform. Give them a couple more years and I think they will work out the kinks.

Incentivized