Appmixer vs Apache Kafka: Which is a better fit?

Oytun O

CTO

Appmixer platform is very flexible and comes with a good set of components. You can access and modify these components' source code, which is a great help.

Edmund E

Senior Product Manager

Documentation can be missing in some places, and there have been a few quirks leftover from earlier iterations of the product.

Edmund E

Senior Product Manager

The ability to host the solution ourselves and extend it with our own code. This made processes around security and privacy significantly simpler as it is running on our own infrastructure.

UI/UX could be simpler/easier. Sometimes it crashes with poor UO feedback.

I like the ease of embedding it into our own app. It fits in nicely, both from a design as well as from a technical pov.

I really like the breadth of integrations and the quality of support.

Ahmed A

CEO

The feature set is just amazing, it enables you to build resilient and fault tolerant applications with ease.

Srikar S

Software engineer

Though it has various messaging capabilities, kafka has poor debugging and logging tools to monitor an app communication topic which is risky.

The functionality of kafka is just so good, everything works fine and nothing breaks any time. Also the distribution is really good.

Whenever we publish data from producers to Kafka, it is stored in a buffer and then it is published to Kafka, so we need to always flush the buffer to keep it empty.

Sakshi S

Infrastructure Engineer

The best thing is architecture which I like the most and it is easy to understand/learn how exactly Kafka works.

It’s a bit hard to maintain when you have a large kafka cluster with a lot of topics.

Riya R

Software Engineer

It is an open source which can handle real time data, Due to its scalability and fault tolerance it is the best choice for the large amount of real time data processing.

It matches only exact topic name and does not support wildcard topic selection.