.. _cloud-limits: Supported Features for |ccloud| =============================== This topic provides the supported features and limitations for :ccloud-cta:`Confluent Cloud|`. .. _feature-capability: Features in |ccloud| -------------------- The following limits and features apply to all |ccloud| cluster types: ============================ ====================================================================== Description Supported ============================ ====================================================================== ACLs Yes. For details, see :ref:`acl-manage`. Auto topic creation No Consumer lag UI Yes. For details, see :ref:`vpc-dash-access`. Encryption at rest Yes (encrypted volumes) Encryption in motion Yes (SSL/TLS) Exactly Once Semantics Yes Key based compacted storage Yes Multi-zone high availability Yes Service accounts Yes. For details, see :ref:`service-accounts`. Support Yes. For details, see :ref:`cloud-support`. Topic management UI Yes. For details, see :ref:`cloud-topics-manage`. Max topics Depends on provisioned storage capacity and total cluster size. |sr| Yes. For details, see :ref:`sr-prv-ft`. ============================ ====================================================================== The following limits and features apply to specific |ccloud| cluster types (where applicable, limits are pre-replication): ================================== ========================= ========================== ============================================ Description Basic Standard Dedicated ================================== ========================= ========================== ============================================ Cluster throughput - Write: Up to 100 MB/s - Write: Up to 100 MB/s - Write: Up to 50 MB/s per CKU - Read: Up to 100 MB/s - Read: Up to 100 MB/s - Read: Up to 150 MB/s per CKU Max partitions per cluster 2,048 2,048 4,500 per CKU up to 33,000 total Max storage per partition 100 GB 100 GB 100 GB Data retention per cluster Up to 5 TB Up to 5 TB 10 TB per CKU Max message size 2 MB 2 MB 2 MB default, but can be increased to 8 MB Max simultaneous connected clients 100 100 1,000 per CKU Max connection attempts per second 10 10 80 per CKU Max requests per second 1,500 1,500 15,000 per CKU Network peering options Not available Not available VPC Peering, Transit Gateway on |aws| Uptime SLA Not available 99.95% 99.95% Multi-zone high availability Not available Available Available |ccloud| |sr| schema versions 1,000 1,000 1,000 Max tasks per connector 1 Unlimited Unlimited ================================== ========================= ========================== ============================================ .. _providers-regions: Cloud Providers and Regions --------------------------- .. include:: ../includes/cloud-support.rst .. _cloud-support: Compliance for |ccloud| ----------------------- .. include:: ../includes/compliance.rst Upgrade Policy for |ccloud| --------------------------- This section describes how changes to |ccloud| are managed for :ref:`minor-ccloud-upgrade`, :ref:`major-ccloud-upgrade`, and :ref:`deprecation-ccloud-upgrade`. .. _major-ccloud-upgrade: .. _minor-ccloud-upgrade: --------------------------- Minor Upgrades for |ccloud| --------------------------- Any change to |ccloud| services that isn’t a major upgrade or deprecation. Potential customer impact - Minimal: standard |ak| state changes that clients handle gracefully, for example leader elections. - None: totally transparent, depending on customer usage of the service. Examples - |ak| cluster roll. - Upgrading |ak| to a fully backwards-compatible version. - Adding net new features. Frequency Very often, e.g., multiple times per day. Communication before the change May include email notifications, in-app messaging, updated documentation and release notes, and/or communication from Sales and customer operations. Timing of the change for each customer 100% at Confluent’s discretion. --------------------------- Major Upgrades for |ccloud| --------------------------- Any change to |ccloud| services that requires code changes to any customer applications (|ak| clients, API integrations, etc) to continue working as before. Potential customer impact - Large: could prevent use of service without code or configuration changes, or could problematically alter the performance profile. - None: totally transparent, depending on customer usage of the service. Examples - Upgrading |ak| to a version that is not fully backwards-compatible with the previous version. - Updating a public API from ``api/v1/foo`` to ``api/v2/foo``. - Security update that materially changes cluster or client throughput. Frequency Rare (~1 per year) Communication before the change - Guaranteed: multiple email notifications to all registered |ccloud| users, starting at least 180 days before the upgrade date, with details about the change and available options. - May also include: in-app messaging; updated documentation and release notes; communication from Sales and customer support. Timing of the change for each customer May be coordinated with |ccloud-ent| customers to avoid high-risk times and make the upgrade sooner, but the final date set by Confluent is not negotiable. .. _deprecation-ccloud-upgrade: ------------------------- Deprecations for |ccloud| ------------------------- Any removal of customer-usable functionality from |ccloud| services. Potential customer impact - Large: could prevent use of service if the customer relies on the feature. - None: totally transparent, depending on customer usage of the service. Examples - Complete removal of a feature from the UI. - Shutting down ``api/v1/foo``. - Removing a particular Connector as an option. Frequency Rare (~1 per year) Communication before the change - Guaranteed: multiple email notifications to all registered |ccloud| users, starting at least 180 days before the deprecation date, with details about the change and available alternatives. - May also include: in-app messaging; updated documentation and release notes; communication from Sales and customer support. Timing of the change for each customer 100% at Confluent’s discretion. Notes Deprecations may be part of major upgrades (no guarantee of equivalent functionality in new versions). Customer Support for |ccloud| ----------------------------- ==================== =============================== ========================================= Description |ccloud-ent| |ccloud| ==================== =============================== ========================================= Support Business (included): Basic - 24 x 7 coverage - `Community`_ only - P1 issue response within 60 minutes Developer Premier (add-on): - Business hours support - 24 x 7 access to support portal - 24 x 7 coverage - P1 issues response within Business 30 minutes - Assigned TAM, quarterly - 24 x 7 coverage business and technical - 60 minutes response SLA reviews For more information, see :ref:`cloud-change-support` ==================== =============================== ========================================= .. _Community: https://slackpass.io/confluentcommunity .. _sr-prv: ----------- |sr-ccloud| ----------- :ref:`schemaregistry_intro` is fully supported on |ccloud| with |sr|. Details are listed below. .. _sr-prv-ft: Supported Features for |sr-ccloud| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - A single |sr| is available per Environment. - Access Control to |sr| is based on API key and secret. - Each Environment must have at least one |ak-tm| cluster to enable |sr|. - .. include:: ../includes/vpc-sr.rst - Available in cloud provider regions located in the US, Europe, and APAC. Learn More ^^^^^^^^^^ - To get started with |sr| on |ccloud| see :ref:`cloud-sr-config`. - For information about moving some or all on-premises schemas to |ccloud|, see :ref:`schemaregistry_migrate`. - For information on how to manage space per |ccloud| limits and free up space for additional schemas, see :ref:`sr-in-cloud-free-up-space` in the Developer Guide. .. _connect-ccloud-preview: ------------------------ |ccloud| Connect Preview ------------------------ Certain |ccloud| connectors are available as preview features. A preview feature is a component of |cp| that is being introduced to gain early feedback from developers. These features can be used for evaluation and non-production testing purposes or to provide feedback to Confluent. Comments, questions, and suggestions related to preview features are encouraged and can be submitted to ccloud-connect-preview@confluent.io. Refer to |ccloud| :ref:`connector limitations ` for details. .. _dataflow-ccloud-preview: -------------------------- |ccloud| Data Flow Preview -------------------------- |ccloud| Data Flow is currently available as a preview feature. A preview feature is a component of |cp| that is being introduced to gain early feedback from developers. These features can be used for evaluation and non-production testing purposes or to provide feedback to Confluent. Comments, questions, and suggestions related to preview features are encouraged and can be submitted to ccloud-dataflow-preview@confluent.io. For more information, see :ref:`ccloud-data-flow`. .. _ksql-optin-ccloud-preview: ------------- |ccloud| KSQL ------------- You can provision KSQL applications by using the |ccloud| UI or the ccloud CLI. For more information, see :ref:`cloud-ksql-create-application`. .. _ksql-prv-ft: Supported Features for KSQL in |ccloud| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Web interface for managing your KSQL cloud environment directly from your browser that exposes all critical KSQL information. - SQL editor to write, develop, and execute SQL queries with auto completion directly from the Web interface. - Integration with |sr-ccloud| to leverage your existing schemas to use within your SQL queries. - Available in AWS, GCP, and Azure in all regions. New Features for KSQL in |ccloud| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - New built-in functions: - COUNT_DISTINCT(v) - aggregate function, computes the number of distinct values of ``v``. - CUBE_EXPLODE(a) - tabular function, outputs a row for each unique combination of elements in array ``a``. - Expression support for joins: .. code:: sql SELECT * FROM s1 JOIN s2 ON s1.str = SUBSTRING(s2.str, 3) EMIT CHANGES; - Native Map and Array constructors: .. code:: sql SELECT ARRAY[1, 2] FROM s1 EMIT CHANGES; SELECT MAP(k1:=v1, k2:=v1*2) FROM s1 EMIT CHANGES; - Expression support for PARTITION BY: .. code:: sql SELECT col0, col2, col3 FROM s1 PARTITION BY SUBSTRING(col2, 1, 4) EMIT CHANGES; - Improved error messages: ACL-related errors link to relevant ACL documentation. Limitations for KSQL in |ccloud| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Currently, user-defined functions (UDFs, UDAFs, and UDTFs) aren't supported. - You can have a maximum of 20 continuous queries per application. - You can have a maximum of three KSQL applications. - Pull queries aren't supported. - |kconnect| integration isn't supported. - ccloud CLI version 0.198.0 or higher is required to create ksqlDB API keys for |ccloud|. Pricing ^^^^^^^ The unit of pricing in |ccloud| KSQL is the *Confluent Streaming Unit* (CSU). A CSU is an abstract unit that represents the linearity of performance. For example, if a workload gets a certain level of throughput with four CSUs, you can expect about three times the throughput with 12 CSUs. Confluent charges you in CSUs per hour. You select the number of CSUs for your application at provisioning time. You can configure CSUs in blocks of four. - 4 CSUs is the minimum. - 12 CSUs is the initial maximum. - Your application can have 4, 8, or 12 CSUs. .. note:: CSU pricing varies slightly depending on cloud provider and region. Pricing is shown in the web interface as part of KSQL provisioning so that you can see exact pricing for your cloud and region of choice. Scaling CSUs ^^^^^^^^^^^^ Scaling your application's CSUs after initial provisioning is not supported. If you determine that your application requires more CSUs, you must provision a new application with the desired number of CSUs, and :ref:`migrate your old application ` to your new one. Sizing guidelines ^^^^^^^^^^^^^^^^^ Four CSUs are sufficient for many workloads. In general, start with four CSUs and scale out if more capacity is needed. To identify when more CSUs are needed, check KSQL consumer lag. After your KSQL application is provisioned, you can only change the CSU allocation by :ref:`migrating your old application ` to a new one one with the desired number of CSUs. .. toctree:: :maxdepth: 1 cluster-types