Three: The Challenge of Matching a Solution to the Current Technology Stack
The previous part has shown us how data security can be a challenge in embedded reporting.
Embedded tools must match up with the technology stack.
If the application does not match the existing stack, it will be critical to have a plan for bridging those gaps. When these gaps exist, finding a solution is rarely simple or cost-effective.
Decision makers must take several things into consideration before settling on an embedded reporting application, including:
- Whether the solution will be self-hosted or hosted in the cloud.
- Does the solution utilize third-party tools like Adobe, Flash, or Java? These platforms come with risk, and it’s important to know what the organization is opening itself up to by integrating these plugins.
- What operating system is required? Does it require a Windows Server architecture, Linux, Oracle, SQL, etc.?
- How reporting aligns across different platforms, including mobile.
In order to avoid potentially costly mistakes, decision makers must consider their existing technology and have a plan in place to bridge any gaps before choosing an embedded reporting solution for their existing platforms and products.
In the next part, you will learn how the scalability can be a challenge in embedded reporting.