Magic xpi Integration Platform vs. SPS Commerce vs. WSO2 API Manager

In our experience, the product performs really well when interfacing systems with ERP's through SQL server database tables, but we've even made some interfaces with the web service functionality included with the magic xpi integration platform. Also, we've made some SAP Business One - SAP Business One interfaces, for copying information from one company to another.

Incentivized

When you find yourself growing and finding success faster than you can keep up with, SPS Commerce will save your life and your reputation. The services they offer are easy to understand, they are available with suggestions and ideas for better ways, personalization is available to best suit your needs or the needs of your customers so that you can really shine and relieve the worries that come with growing pains. SPS also helps to keep information accurate with less human touching to cause errors.

Incentivized

It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?

Incentivized

• The UI is really simple to use, you have source / destination mapping for the items.
• The scheduler gives you a lot of options when executing the models.
• The error handling is usually pretty good and the errors can be corrected fast.

Incentivized

• We can easily create and send order confirmations.
• We respond to the corresponding receiving departments with timely and accurate ASN's.
• Once the order has shipped, customer service utilizes the invoicing function.

Incentivized

• Authentication based on OAuth 2.0 and HTTP Basic Authentication.
• Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
• Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
• Mediation to perform transformation, orchestration etc.

Incentivized

• Although the scenarios may be online, the main service usually freezes and the processes can't transact any data. With a single restart of the service, the processes will be functioning again.
• The support for more applications would be nice, even though there is a nice number of them.
• The licensing for the software may be a little confusing.

Incentivized

• We have quite a few people here who use this portal, and we have it set up to receive an email when an order is available to print. As of now, you can only add a few recipients to receive those emails; it limits you.
• Invoicing is challenging at times as you have to remember to go in and invoice. If you forgot, it is hard to find the order to invoice, as it seems to disappear.
• We still haven't figured out how to have some of the invoicing features auto-populate, so there isn't so much to fill out. I wish some of those features were easier to use, or find if you have them.

Incentivized

• Better QA testing prior to releases rollout
• Better support needed

Incentivized

If I can drop it, I will this year. We gave it a decent try for over 4 years and it has gotten worse with each added connection.

Phone support is generally very good and you can get a person on the phone within a few minutes. Their emailed customer support however is very poor and often goes several days or longer before receiving a response, if ever at all

Incentivized

Honestly, we have only used and evaluated magic xpi platform because of the recommendation of our SAP Business One main supplier, who has previously used the platform for their developments. So far, we have no regrets with the acquisition of the platform and we are very happy with it's performance until now.

Incentivized

In my opinion, SPS Commerce is the bottom out of all three provided here. I think, essentially, if you are looking to be hands off and only oboard on setup and don't plan on growing your business and want to not understand anything about EDI and how it affects your company, SPS Commerce is a fine choice. Just if you want to do anything beyond that, I believe you are going to have the worst time.

Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.

Incentivized

• The implementation time for this kind of projects has been greatly reduced.
• Certifying an In-House resource in the Magix xpi platform is probably the best option, considering all of the projects that can be developed in the future without the need of an external consultant.
• The processes that have been automatized with the Magic xpi platform helped reduced human error and the time those processes took to finish.

Incentivized

• I enrolled in a product I ended up not using because the vendor that required it ended our working relationship and SPS refused to offer a refund. After I canceled it, they continued to charge our account for three more months of service.
• The interface is simple and easy to understand and use, so it saved time when preparing shipments.

Incentivized

• We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
• Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
• Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.

Incentivized