Apache Kafka is an open-source stream processing platform developed by the Apache Software Foundation written in Scala and Java. The Kafka event streaming platform is used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.
N/A
Microsoft Dynamics GP
Score 5.1 out of 10
N/A
Microsoft Dynamics GP is an ERP software with accounting capabilities. It includes various packs for customizability and features tailored to specific industries’ needs. GP is offered as a perpetual license or subscription.
N/A
SAP Cloud ERP
Score 8.6 out of 10
N/A
SAP Cloud ERP (SAP S/4HANA Cloud) is a modular ERP that enables users to run mission-critical operations in real time from anywhere, introduce new business models in any industry, and expand globally. SAP Cloud ERP is a SaaS product and can also be deployed in a hybrid landscape for quicker time to value. SAP Cloud ERP is a foundational component of the
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.
Microsoft Dynamics GP is well-suited for our environment, as we pay a diverse group of employees, including on-the-road drivers, shop employees (some in other locations), and office employees. It easily tracks time off, taxes, pay, etc. The reporting allows us to verify with our drivers how they are paid each week, whether it be through mileage or stop-offs.
It is an appropriate ERP solution for all types of companies. It offers faster data processing, along with modern technologies such as built-in AI, machine learning, and real-time data analytics. It comes with built-in AI that helps reduce manual work by automating repetitive tasks, providing real-time insights, and offering proactive recommendations for important business decisions.
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).
Great Plains started as back office/accounting, and that is still it's strong suit.
SQL and the GP programming language, Dexterity, provide a robust, scalable, and stable platform with well documented maintenance and repair procedures. Relatively easy to manage, tune, and support.
Microsoft support for GP verges on "particularly well". Doesn't quite get there but good enough once you know what you're doing
Strong partner network, including the GP User Group (GPUG)
The software helps in forecasting and identifying potential challenges that would affect our organisation in the near future. This enables us to prepare in advance and also adopt practical and viable measures.
It enables faster and accurate data processing, which enhances decision-making.
It's easily customizable according to specific organizational needs. This promotes overall efficiency and productivity of the organization.
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
With respect to the allocations, once the expense is entered into the allocation account, you lose the ability to run any detail on just the total of the expense. It would be nice if you could run a trial balance on the allocation accounts the same way you can with regular accounts.
I've always thought security set up could be a bit simpler. It actually has gotten better through the years. Specifically, with eight separate entities, it would be nice to have a "master" setup where you could call up one group entity, assign the users rights, and then be finished. Currently, whenever I have a new user, I have to call up each individual entity and select all of the features I want the user to have. That means I have to do eight steps for each user.
Due the economic challenges that Puerto Rico is having, the company has had to merge some companies in order to be more efficient. It has been easy in GP to process those merges, even thought we had to spend days to accomplish that the process was smooth and accurate. In addition we were able to streamline the purchasing and sales process and the organization is confident to keep renewing GP for the future versions.
The cost of SAP as an ERP is quite high and the switching costs associated with ERP systems are even higher. That being said moving from one ERP to another only happens once in a great while for large organizations. Those switching costs include retraining, IT hardware requirements, outside consultants and more
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
Though it is a basic accounting package, I believe some users do not find the old style menus and navigation options intuitive. There is also a great lack of training resources in the market, so users have to learn the product without guidance a lot, resulting in inefficient workflows and misuse or misunderstanding of many features.
Mostly great for building trust; however, the system could be more user-friendly. Sometimes the systems are slow. We also need to find a way to simplify user support. It can be very complex to support an SAP system. The confusion/deep expertise creates an ROI issue as professionals can be expensive to hire.
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.
The support system I find great as whenever I run into problems they rectify them quickly as possible they never reacted late the support is just up to the mark for me. They provide many solutions to the problems I faced the [technical] team support is always amazing they [listen] to mean work accordingly.
Basically the challenge with this implementation was the Business Portal, too many errors and even the aplication is up and running the users are still having issues. We will start planning the migraton to GP 2015 soon.
SAP requires a lot of internal and external resources to complete its successful implementation. The cloud version requires a deeper understanding of the different capabilities of the local systems (hardware) and the connection towards your local IT team. We found several problems on our systems that we couldn't foresee before the implementation and roll out.
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.
I come from a strong background of using SAP. SAP doesn't have the flexibility of GP, an example would be SAP doesn't allow core mods, if they catch you, you lose support. Microsoft doesn't really care about mods, but they will be quick to have the vendor you used support your issue if it is caused by those mods. With SAP your company adapts to the software, where with GP you adapt the software to you.
The platform utilizes advanced predictive analytics to anticipate operational bottlenecks and put them out of commission before the problems become larger. We can proactively develop effective strategies that help keep service quality in the face of unexpected changes in the market, or external disruptions, by continuously analyzing historical performance data as well as elements of the current market
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.
Microsoft Dynamics GP allows my clients to move from a paper or spreadsheet based company to an integrated, electronic, streamlined business. I love being able to help clients gain efficiencies through the use of Microsoft Dynamics GP.
Microsoft Dynamics GP allows for better customer service because everything is at our fingertips. If someone calls questioning an invoice, we can easily look it up. If someone calls stating they paid an invoice with a certain check number, we can quickly run a query to find that particular check number to see where it was applied.
Having everything on a single platform provides ease of use for upgrades, backups and end user training. There is only one software to learn!
