Azure Synapse Analytics is described as the former Azure SQL Data Warehouse, evolved, and as a limitless analytics service that brings together enterprise data warehousing and Big Data analytics. It gives users the freedom to query data using either serverless or provisioned resources, at scale. Azure Synapse brings these two worlds together with a unified experience to ingest, prepare, manage, and serve data for immediate BI and machine learning needs.
$4,700
per month 5000 Synapse Commit Units (SCUs)
Benchling
Score 8.9 out of 10
N/A
Benchling’s cloud platform is used by pharmaceutical and biotech companies to analyze complex datasets, streamline research workflows, design DNA using CRISPR gene-editing technology and more.
It's well suited for large, fastly growing, and frequently changing data warehouses (e.g., in startups). It's also suited for companies that want a single, relatively easy-to-use, centralized cloud service for all their data needs. Larger, more structured organizations could still benefit from this service by using Synapse Dedicated SQL Pools, knowing that costs will be much higher than other solutions. I think this product is not suited for smaller, simpler workloads (where an Azure SQL Database and a Data Factory could be enough) or very large scenarios, where it may be better to build custom infrastructure.
Benchling is especially well suited to groups or contexts where there are many users who do not have a coding background but need a seamless and structured approach to data. Benchling is particularly useful in cases where there are data flows from instruments and other devices where the data can be deposited in an automated fashion. It is likely less appropriate or useful to users who are just looking for a general data warehouse solution.
It takes some time to setup a proper SQL Datawarehouse architecture. Without proper SSIS/automation scripts, this can be a very daunting task.
It takes a lot of foresight when designing a Data Warehouse. If not properly designed, it can be very troublesome to use and/or modify later on.
It takes a lot of effort to maintain. Businesses are continually changing. With that, a full time staff member or more will be required to maintain the SQL Data Warehouse.
Some of the integrations can be a bit spotty so it depends on what kind of data source you are integrating
Sometimes new users are not always aware of all the various functionality that Benchling has - can do better to provide more user awareness of more complex features
The data warehouse portion is very much like old style on-prem SQL server, so most SQL skills one has mastered carry over easily. Azure Data Factory has an easy drag and drop system which allows quick building of pipelines with minimal coding. The Spark portion is the only really complex portion, but if there's an in-house python expert, then the Spark portion is also quiet useable.
Microsoft does its best to support Synapse. More and more articles are being added to the documentation, providing more useful information on best utilizing its features. The examples provided work well for basic knowledge, but more complex examples should be added to further assist in discovering the vast abilities that the system has.
When client is already having or using Azure then it’s wise to go with Synapse rather than using Snowflake. We got a lot of help from Microsoft consultants and Microsoft partners while implementing our EDW via Synapse and support is easily available via Microsoft resources and blogs. I don’t see that with Snowflake
Benchling was much more of a full stack solution and provide much more features that were relevant to the group. Airtable was more of a generic way to manage large amounts of data, but the complexity was still high for the types of data that would be need to be managed and there would need to be some workarounds. Overall Benchling was selected since it also had an electronic lab notebook feature which was very useful to associates in addition to its data workflows.
It had a positive ROI in terms of reducing the amount of time spent on data movement and curation by associates
It had a positive ROI in terms of increasing the number of insights from structured data
It reduced the number of data entry and analysis errors by associates which led to a positive ROI in terms of efficiency and reducing time wasted by tracking down errors in data
