Apache Kafka vs. Volusion

Apache Kafka is well-suited for most data-streaming use cases. Amazon Kinesis and Azure EventHubs, unless you have a specific use case where using those cloud PaAS for your data lakes, once set up well, Apache Kafka will take care of everything else in the background. Azure EventHubs, is good for cross-cloud use cases, and Amazon Kinesis - I have no real-world experience. But I believe it is the same.

Volusion is a good company if you're starting out. The problem is that, if you want more complexity out of the program, you're kind of stuck. Also the regular time out errors and slow downs can be very frustrating. Packages that miss overnight deadlines because your system stops working can cost you customers. In today's highly competitive market, that's just something that's hard to put up with. If you have a lower volume of business you might be able to work around these issues.

Incentivized

• Really easy to configure. I've used other message brokers such as RabbitMQ and compared to them, Kafka's configurations are very easy to understand and tweak.
• Very scalable: easily configured to run on multiple nodes allowing for ease of parallelism (assuming your queues/topics don't have to be consumed in the exact same order the messages were delivered)
• Not exactly a feature, but I trust Kafka will be around for at least another decade because active development has continued to be strong and there's a lot of financial backing from Confluent and LinkedIn, and probably many other companies who are using it (which, anecdotally, is many).

Incentivized

• Templates are pre-built for a good end user experience. I've gone through the process of building custom sites as well as tweaking both free and paid templates that Volusion's design team provides.
• Their support team didn't use to be as helpful, but in recent years have answered nearly all questions I've had. Their support section within the database provides detailed walkthrus as well.
• Order processing is easy once you've been trained on the system. We got to a point where nearly the entire process was automated from initial purchase through shipping.

Incentivized

• Sometimes it becomes difficult to monitor our Kafka deployments. We've been able to overcome it largely using AWS MSK, a managed service for Apache Kafka, but a separate monitoring dashboard would have been great.
• Simplify the process for local deployment of Kafka and provide a user interface to get visibility into the different topics and the messages being processed.
• Learning curve around creation of broker and topics could be simplified

• API calls use the previous call as a reference, even if you weren't the one we made the previous call. Can lead to data gaps, so you often have to set a manual date range to look back to make sure you aren't missing any data.
• Not as customizable as most ecommerce platforms
• Not as many integration options as most platforms

Incentivized

Kafka is quickly becoming core product of the organization, indeed it is replacing older messaging systems. No better alternatives found yet

Incentivized

When you spend so much time with a product like this and not only have you witnessed its growth, but you almost feel like you are next those that make the decisions of building features a certain way, you can't help but want to stay and be a part of their continued growth. It's simply a great product. Can it improve? By all means! But it will only improve because of users and avid resellers like me.

Apache Kafka is highly recommended to develop loosely coupled, real-time processing applications. Also, Apache Kafka provides property based configuration. Producer, Consumer and broker contain their own separate property file

Incentivized

I know what to do to add a new product, promotion or do an analysis of sales.

Incentivized

Support for Apache Kafka (if willing to pay) is available from Confluent that includes the same time that created Kafka at Linkedin so they know this software in and out. Moreover, Apache Kafka is well known and best practices documents and deployment scenarios are easily available for download. For example, from eBay, Linkedin, Uber, and NYTimes.

Incentivized

You have to wait on hold for at least 45 minutes every call—the tech support person never knows the answer right away so they put you on 10 minute holds only to come back and say they're still looking for answers. The chat function could take days to get a response. Our "Dedicated Account Manager" never checks in or answers, nor are they ever in the office when we call. It's like they try to be as unavailable as possible until you forget why you even called in the first place. Insane.

Incentivized

It is best to use the built-in features and recommended services for the most turn-key experience (ie. Skipjack for payment processing so that it can all be done from the Volusion backend).

I used other messaging/queue solutions that are a lot more basic than Confluent Kafka, as well as another solution that is no longer in the market called Xively, which was bought and "buried" by Google. In comparison, these solutions offer way fewer functionalities and respond to other needs.

Incentivized

While k-eCommerce was very glamorous to us because it integrates with our main workflow, it just didn't have some of the marketing features that are so integral to the way we do business online. The set-up costs were also way too high. Volusion is so affordable and feature heavy, it makes it very difficult for any shopping cart provider to compete. You can find others who are competitively priced and have similar features, but they simply aren't as robust (at least for the way we use it)

• Positive: Get a quick and reliable pub/sub model implemented - data across components flows easily.
• Positive: it's scalable so we can develop small and scale for real-world scenarios
• Negative: it's easy to get into a confusing situation if you are not experienced yet or something strange has happened (rare, but it does). Troubleshooting such situations can take time and effort.

Incentivized

• Honestly, when you're in the dashboard, the UX is simply horrendous. I mean, everything that should be 1-2 clicks away is 4-6 clicks away, and each pages takes at least four seconds to load. You just find yourself wasting a lot of time waiting for things to load. This should be more simple.