AWS Batch vs. Tidal by Redwood

More appropriate if you have a tech group that can use more of the AWS Batch rather than one or 2 things. It works great for me, but there was a huge learning curve the first week of using it. Now, I love it - and I hope to dig deep into other parts not just S3.

Incentivized

On coming to well suited experience while error handling and effortless recovery processes are crucial, Tidal performs exceptionally well. It can identify and fix automated issues, reducing downtime and interruptions. A smaller automation solution may be more cost-effective if a business primarily utilizes a single platform or uses a small number of applications that do not require complex integration.

Incentivized

• Easy to orchestrate and trigger jobs
• No time limit issues like lambda
• Multiple Jobs can be run in same single compute and job queue
• JOb queue can queue up task for parralled or serialization

Incentivized

• Tidal Automation allows us to automate and schedule/ perform various tasks in a easy and effective manner. It is highly interactive and effective allowing nearly 4k -5k jobs to run a day.
• Tidal is designed to be easily shareable and collaborative allowing multiple users to work at a particular time making work effective.
• Tidal allows us to ensure that every event which is triggered is exactly when it's supposed to be regardless of other activities which are going as well.
• It is user-friendly to generate the reports required of a particular object and allows us to test the codes perfectly well before executing in live environment.

• Jobs monitoring dashboards are not matured
• Documentation and support is something which can be improved
• Sometime i faced the slow response or slow in performance i would say

Incentivized

• Still a bit slow when navigating. If you close a job you have to wait a few seconds to open another one. Even when you made no changes.
• When viewing a job and make no changes, the "ok" button changes the last modified date as if you made a change. No big deal, but wastes time when troubleshooting a problem and looking into what jobs were changed last.
• You can see the parameters column in the "job activity", but not in "Job definitions".
• Can't search the parameters field in the filter.
• Changing a variable name does not change it on the job. It still works because Tidal Automation uses the ID number. It just causes confusion when you see a variable on a job and can't find the variable under "Variables". On top of that, Tidal Automation does not show the ID column under "Variables" making it even more difficult to find the variable.

We are on the fence. The increased pricing for renewals is staggering. With new automation options like Microsoft's Power Automate and Event Driven Ansible on the field, there are other options now available.

Key advantages include cost-effectiveness through dynamic resource provisioning and the use of spot instances. It auto-scales to meet workload demands, allowing easy job submission via the AWS Management Console or SDKs. It integrates seamlessly with other services like S3 and CloudWatch. It features automatic retries for failed jobs. It allows for a custom computing environment tailored to specific needs

Incentivized

Having provided consulting services for years on Tidal by Redwood, I recommend going with a solutions partner or consultant to deploy it. I believe there are sizing and tuning guidelines that should be followed for environments of scale. I believe they are not critical when first lighting up the product, but if you are not aware of them you will encounter performance degradation after a few thousand job objects are added.

We wanted to start everything on a scale & with fewer resources to manage the underlying infrastructure.

Incentivized

1. Tidal is good at processing large volume pf data and is cost effective. 2. Tidal can automate the scheduling of production objects, ensure that materials are delivered on time 3. Tidal Process large volumes of data which cannot be done everyday by running codes/scripts manually which does it with ease when required.

Incentivized

• Overall over business is able to save the cost
• Saved our times to improve the existing process
• Able to integrate with other applications as well, so that is plus point

Incentivized

• Better decision-making and more process visibility are achieved through reporting and monitoring.
• Lowered time frames and streamlined administration of the workflow.
• Improved cost and resource allocation, especially in cloud contexts.
• A decrease in manual errors and related expenditures.
• Unusual problems that could occur during automation.
• Possible difficulties shifting to a new automation tool.
• The expense of beginning implementation and training.

Incentivized