The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Choose Databricks serverless compute when your workload fits its supported APIs, data access, networking, job-task, and streaming constraints; Databricks manages the infrastructure. Choose classic compute when a documented serverless limitation blocks the workload or you need customer control over compute configuration. The right choice depends on the workload, so check the current limits and test before moving production jobs.
This comparison reflects Databricks documentation for AWS, with cited pages last updated September 11–29, 2026. Availability and recommendations can differ by cloud, region, task, and runtime.
As an Amazon Associate I earn from qualifying purchases.
What is the difference between classic and serverless compute?
With classic compute, customers create, configure, and manage all-purpose, jobs, and Lakeflow pipeline compute resources in their cloud provider account. With serverless compute, Databricks manages the infrastructure. That operational distinction does not mean one option is universally cheaper or faster.
For the general compute overview, see Databricks’ classic compute overview and its compute documentation.
#1 Best Overall
Which serverless limitations should you check first?
Compare the workload itself—not just its cluster settings—with the current serverless compute limitations. These constraints commonly determine whether serverless is viable:
- Language and APIs: R and Scala notebooks are unsupported. Serverless supports Spark Connect APIs, not Spark RDD APIs. Because Spark Connect can defer analysis and name resolution until execution, code may behave differently than it does on classic compute.
- Data access and paths: External data sources must be accessed through Unity Catalog. DBFS access is limited; Databricks points users to Unity Catalog volumes or workspace files instead. Relative paths and imports can fail because the working directory is not guaranteed.
- Compute-scoped configuration: Compute policies, init scripts, libraries, instance pools, event logs, and most Spark configurations are unsupported. You may need notebook-scoped dependencies or a serverless-specific configuration.
- Diagnostics: The Spark UI and Spark logs are not available in serverless in the same way as on classic. Databricks points users to query profiles and client-side application logs for diagnostics.
- Streaming triggers: For Structured Streaming jobs,
Trigger.AvailableNow()and deprecatedTrigger.Once()are supported; continuous and processing-time triggers are not. This job restriction should not be applied to Lakeflow pipeline modes: the pipeline documentation says its trigger limitations do not apply to pipeline modes. - Job duration: A serverless job can run for a maximum of seven days. Longer work must be split or run on classic compute.
- Task type: The current jobs matrix lists JAR and Spark Submit as classic jobs, while recommending serverless for many notebook, Python, SQL, pipeline, and dbt task types. Confirm the exact task in the jobs compute matrix.
This is a decision-focused selection, not a replacement for the complete, frequently updated limitations page.
When does serverless make more sense?
Lakeflow pipelines
Databricks recommends serverless for Lakeflow pipelines that do not hit classic-only limitations. Its documented advantages include Databricks-managed infrastructure, incremental refresh for materialized views, vertical and horizontal autoscaling, and less need for cluster creation permissions. Classic pipeline compute requires the customer to configure compute, policies, and instance types.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The documented pipeline exceptions include legacy Hive metastore use, private networking unsupported by serverless, and a workspace region where serverless is unavailable. Verify the requirements for the actual workspace in Databricks’ pipeline comparison.
Rank #3
- Your Personal Streaming Server - Build your own Netflix-style media library and stream 4K movies, shows and photos to any device without monthly fees
- Create Your Own Cloud - Store your entire photo, video and music collection; access from anywhere with fast 282 MB/s transfer speeds
- Creator-Grade Backup Solution - Protect your irreplaceable content with automated backups to cloud services, external drives and remote NAS
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Smart Home Surveillance - Support up to 30 IP cameras with AI detection, instant alerts and secure remote monitoring
Jobs
Use the task matrix rather than a blanket rule. It recommends serverless for multiple common task types, but currently puts JAR and Spark Submit jobs under classic compute. The matrix is the relevant check for the job you plan to run.
How should you assess a migration?
Databricks says many classic workloads can move with minimal or no code changes, but its migration guide calls out patterns that need changes or remain unsupported, including RDD APIs and DataFrame cache APIs. It describes a quick compatibility test using classic compute with Standard access mode and Databricks Runtime 14.3 or above. That is vendor guidance, not proof that a particular workload will pass.
- Inventory the workload: Record its task type, language, APIs, data sources, libraries, init scripts, network paths, streaming trigger, and expected runtime.
- Check support: Compare every dependency and requirement with the live serverless limitations and jobs task matrix.
- Adapt only where suitable: Replace unsupported patterns only when a supported alternative meets the need. The migration guide, for example, maps RDD patterns toward DataFrame APIs and suggests removing cache calls.
- Run a representative comparison: Databricks recommends an A/B approach for production: run the same workload on classic as the control and serverless as the experiment. Compare correctness, completion behavior, diagnostic information, and billed cost using current pricing sources.
- Decide with the workload owners: Roll out only after they have checked the results and confirmed operational requirements.
The reviewed documentation does not establish a universal cost winner. A compatibility recommendation also does not guarantee a particular workload’s performance or cost outcome.
Compare the options against your requirements
| Decision area | What to verify |
|---|---|
| Workload compatibility | Supported APIs and languages, task type, streaming behavior, runtime duration, and required libraries. |
| Data and network access | Unity Catalog requirements, DBFS use, private networking, region availability, and IPv4 reachability. |
| Control and operations | Who selects instance types and policies, installs dependencies, manages scaling, and diagnoses failures. |
| Governance and permissions | Catalog requirements, compute creation permissions, policies, and tagging needs. |
| Cost and performance | Results for the representative workload using current pricing; the cited documentation does not establish a universal comparison. |
For the migration steps and compatibility guidance, see Databricks’ classic-to-serverless migration guide.
Quick Recap
Best Value
- COMPATIBILITY: Specially designed to mount Ubiquiti UniFi Cloud Gateway models UCG-Ultra and UCG-Max securely in place
- RACK SPECIFICATIONS: Standard 1U height rack mount bracket engineered for 10-inch rack installations, offering efficient space utilization
- MOUNTING SOLUTION: Provides stable and secure placement for your UniFi Cloud Gateway UCG Max or UCG Ultra device in server room or network cabinet setups
- PACKAGE CONTENTS: Includes one (1x) 1U 10-inch rack mount bracket specifically designed for UniFi UCG Ultra & UCG Max Gateway installations
- INSTALLATION: Purpose-built bracket ensures proper device positioning and reliable mounting in standard 10-inch rack environments
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
