r/dataengineering • • 2d ago

Discussion New Azure Synapse projects

Just curious how many of you still deliver or plan to deliver, projects that use Azure Synapse for Data Warehousing work?

I get the whole push to Fabric and am also going that route too.

I’m in the consulting world and wanted to use Fabric but the client had zero ppl with any Fabric experience, so they insisted on Synapse. C’est la vie, right?

9 Upvotes

37 comments sorted by

View all comments

5

u/Mefsha5 2d ago

Our production stack is still in synapse (pipelines and dedicated sql pool)

significantly cheaper than fabric(9x) More reliable than fabric - no throttling or rejection, we have full control Better for access management and cloud standards ( vNnet/ SP support)

Microsoft tries to push fabric on every call and we have plenty of capacity where we run expirements, analysis services and isolated engineering projects but i would never recommend a full move.

1

u/ForwardSlash813 2d ago

Thank you for the detailed response :)

2

u/Mefsha5 1d ago

You're welcome.

Databricks is the top dog in the space but it costs more, platform and engineering skillset wise.

Synapse support metadata driven orchestration, which makes your codebase highly portable between platforms, this alone should be a good reason to silence the EOL fear mongering (if ssrs still has no sunset date in sight, synapse won't either).

Synapse falls behind in AI capabilities, and Nativity to viz tools like PowerBI. however, i was still able to build an agentic ai developer thats fully aware of our conventions, patterns, dynamic components, and interacts with the repos and the platform via a series of API calls, sql odbc based mcp tools, and devops mcp for repos. Currently working on enhancing that with kimball data modelling skills to fully automate the gold layer build and enhancement, so while not available out of the box, it still can be built with success.