AWS Lake Formation vs SAP NetWeaver Business Warehouse comparison

"I can easily move data from cold storage to regular storage."

"In the shortest form, what I appreciated about AWS Lake Formation was that the schema definition and data cataloging were quite good."

"We use this to reduce latency from minutes to seconds, as we aim for real-time visibility into patient healthcare monitoring."

"The features and capabilities of AWS Lake Formation that I have found most valuable are that it is really convenient to see all the different data assets that were configured and understand who has and what type of service has or does not have access to those services."

"The most valuable features of AWS Lake Formation were the access model itself, as it allows implementation of filters, Blueprints, and row-level and column-level security to mask data that shouldn't be accessed by certain entities, enabling granular control without exposing PII data."

"AWS Lake Formation significantly improves the structure of the data mesh, making it superior to previous structures we used."

"AWS Lake Formation works hand in hand with other products."

"AWS Lake Formation significantly improves the structure of the data mesh, making it superior to previous structures we used."

"The security and audit procedures are the most valuable features."

"It provides us with proof of data, we can centralize all of the information, check it, and then provide the information to our users."

"Transformation is a valuable feature of SAP NetWeaver. I can transform the data as per my needs or my client's needs. For example, flat tables can be transformed with respect to our requirements to combine multiple modules into one single table, and we can derive analytics."

"Data modeling is a valuable feature."

"It's an excellent over-all tool for managers to analyze their business."

"It is a robust system."

"A robust and efficient product."

"The main challenge we faced with AWS Lake Formation was related to cross-account sharing. Granting access to other AWS accounts for tables or databases in a different AWS account was somewhat difficult."

"In our current setup, everyone from my business unit uses the same consumer account. When access is requested for a table, everyone using that business unit account receives access. This could present a security concern, though it benefits new team members who automatically receive all necessary access permissions."

"The solution could make improvements around orchestration and doing some automation stuff on AWS front automation. It would be useful if we could use automation to build images and use hardened images which are CIS compliant."

"In our current setup, everyone from my business unit uses the same consumer account. When access is requested for a table, everyone using that business unit account receives access. This could present a security concern, though it benefits new team members who automatically receive all necessary access permissions."

"Rather than creating an additional hundred tools, optimizing a tool to have a centralized location to do governance would be beneficial."

"The initial onboarding process is challenging because creating a plan takes a month to a month and a half to build out."

"For the end-users, it's not as user-friendly as it could be."

"It falls short when it comes to more granular access control, such as cell-level or row-level entitlements which is a significant drawback for organizations that require precise control over who can access specific rows of data."

"The program is difficult to learn to use"

"It is difficult when your native language is not English. It is difficult for us to explain our issue and also difficult for the technical team to explain a resolution to us."

"There are performance issues in terms of scalability and availability."

"Connectors are complex, and it is difficult to understand or know which connector should be used. For instance, if I want to connect APIs, I will not be able to do it directly. I would have to go to the portal integration to get the data. Therefore, having simplified connectors will make things much easier."

"The product could provide more features."

"I think more integration with other applications would be perfect."

"Design and modeling could be simplified."

"AWS Lake Formation is a bit expensive."

"All SAP products are expensive."

"Pricing is based on the number of user IDs and tyhe user ID works across a suite of products."

"The licensing cost is high for SAP NetWeaver compared to that for other products."