I think the initial schema mapping tool in Striim can have a learning curve when dealing with deeply nested mainframe structures or complex copybooks. A more automated, BA-friendly interface for mapping would be a great addition.
The checkpoints would help me to figure out where the problem was if there's any lag, but I had to do a lot of manual work to figure out where the lag is. Striim would not intuitively tell me the culprit table or database behind the lag. I believe that is an improvement Striim could definitely do. Passwords were an issue. Property variables were not supported for passwords, meaning I had to make sure the password is manually populated. I believe if Striim could read from AWS secrets or its own secret mechanism to store the password, that would really save a lot of time so that I don't have to keep updating the password whenever there is any change. The user experience of triggering alerts if there's any lag which Striim identified, which is outside normal processing time, could intrinsically be done by Striim. I believe that was lacking. I would wait for Striim to tell me, instead of me going and validating whether Striim is lagging behind. If Striim could itself tell me that it's seeing a lot more volume than expected, that would really make me give it a higher number.
Striim offers a comprehensive platform for real-time data integration and streaming analytics, designed to streamline data processes for enterprise-level solutions.Striim enables seamless migration and integration of data across cloud and on-premises environments, making it ideal for businesses looking to leverage real-time analytics. Its capabilities support continuous data flow, reducing latency and enhancing decision-making. Designed for scalable and secure data management, Striim...
I think the initial schema mapping tool in Striim can have a learning curve when dealing with deeply nested mainframe structures or complex copybooks. A more automated, BA-friendly interface for mapping would be a great addition.
The checkpoints would help me to figure out where the problem was if there's any lag, but I had to do a lot of manual work to figure out where the lag is. Striim would not intuitively tell me the culprit table or database behind the lag. I believe that is an improvement Striim could definitely do. Passwords were an issue. Property variables were not supported for passwords, meaning I had to make sure the password is manually populated. I believe if Striim could read from AWS secrets or its own secret mechanism to store the password, that would really save a lot of time so that I don't have to keep updating the password whenever there is any change. The user experience of triggering alerts if there's any lag which Striim identified, which is outside normal processing time, could intrinsically be done by Striim. I believe that was lacking. I would wait for Striim to tell me, instead of me going and validating whether Striim is lagging behind. If Striim could itself tell me that it's seeing a lot more volume than expected, that would really make me give it a higher number.
I think Striim could be improved with better pricing and enhanced documentation.