My main use case for DuckDB is that we're using it as a cache for analytics. We have an embedded analytics product, and in order to manage our compute resources, we are using DuckDB so that we do not compute twice the same query.
The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
My main use case for DuckDB is that we're using it as a cache for analytics. We have an embedded analytics product, and in order to manage our compute resources, we are using DuckDB so that we do not compute twice the same query.
The use of DuckDB as a cache for analytics in an embedded analytics product is a valuable feature. It helps manage compute resources efficiently by preventing repeated computations of the same query. This has made it quite handy and quick to implement, which aligns with the fast-paced needs of our engineering team.
I have been familiar with DuckDB for six months.
Before I landed on DuckDB, we had no other solutions.
When I first implemented DuckDB, I would say something like two hours to make sure everything was working smoothly. It was fairly quick and then we had to tweak it a bit, with some back and forth with our engineering team. I would say it's pretty handy but I would estimate a few hours to get it up and running and then all set.
I have worked with DuckDB. I'm not doing much with DuckDB directly anymore as it's now implemented, so I'm not dealing with it. DuckDB is implemented as a team-wide workflow, but no one works on it on a daily basis. My team did not need formal training on DuckDB as it was pretty intuitive. Adoption has gone pretty well for one department.
SAP HANA serves as an ERP system that covers all modules in the firm, such as the financial process, inventory management, sales and distribution, plant maintenance, and human resources processes. It is comprehensive and also covers quality management, depending on whether the organization's business process is retail or manufacturing, so you will select the needed module for this process.
Implementing SAP HANA offers financial benefits to the organization. Any return on investment (ROI) will be defined before implementing SAP, as if there is no ROI, the organization will not move to SAP. It also relates to the business process performance, and if it improves or solves some issues in the process, it will benefit the firm moving forward.
Whether I or my customers utilize SAP HANA's real-time analytics depends on the data needed to be displayed, and then choosing how to transfer the data to the analytic object, data source, or database to be displayed in the reports. It may be near real-time, real-time, or running batch every day.
There are tools for integration between third-party systems, such as OData or APIs from SAP to get in or push data to other systems.
Support for both structured and unstructured data helps organizations unify data sources depending on the needed data to be displayed. There are many ways to store it for report displays, but structured data will be better than unstructured data.
There is room for improvement in the deployment process as it takes much time and is time-consuming and complex.
I have been using SAP HANA for five years.
Regarding the scalability and flexibility of SAP HANA in adapting to changing IT infrastructure needs, sometimes it may be difficult and sometimes easy. It depends on what needs to change in the structure, as some entities cannot be changed and require a new implementation, while others can be modified.
My thoughts about SAP's technical support are that the first line will be the vendors supporting or providing SAP. If they cannot resolve the issue, I will need to contact SAP with tickets, which will depend on the severity. For standard T-codes or customizing issues, they might direct me back to the vendor who made the customization, but for standard issues, they can support or start working on it.
The number of people from my side usually involved in the deployment process depends on the scale of the organization and the business process, but it is almost a minimum of 22 to 25 persons. It is a combination of engineers and administrators.
Deploying SAP HANA is not difficult. It will always be the gathering of the process or business process from the client and making every point clear and defining it to make the implementation as the best practice.
SAP HANA implementation usually or always takes a minimum of eight or nine months if everything goes okay. The reason it takes so long for SAP HANA is that it depends on the needed modules to be implemented and may be split into many phases to make a smooth transition for the employees to accept these changes and learn how to use the system.
The whole project is quite complex, starting from gathering information, preparing the configuration system, training the team, to the go-live time, and making the go-live process, followed by post-implementation support. All this process may take from eight to nine months or more. I would rate this solution a 9 out of 10.
