# How a Talend Job for Apache Spark works

A Talend Spark Job generates code for either the Spark Batch or Spark Structured Streaming engine, depending on the Job type you select.

A Talend Spark Batch Job can be run in the following runtime modes and environments:

* Amazon EMR
* Amazon EMR Serverless
* Azure HDInsight
* Azure Synapse
* Cloudera Data Engineering
* Cloudera on Cloud
* Cloudera on Premises
* Databricks
* Availability-note[Beta](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-beta)

  Beta content

  Databricks Serverless
* Google Managed Service for Apache Spark (formerly Dataproc)
* Kubernetes
* Local
* Livy Knox
* Spark-submit scripts
* Standalone
* Yarn Cluster

A Talend Spark Structured Streaming Job can be run in the following runtime modes and environments:

* [Preview](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/feature-preview-program-overview.htm)

  Databricks
* [Preview](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/feature-preview-program-overview.htm)

  Local
* [Preview](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/feature-preview-program-overview.htm)

  Yarn Cluster

For details on configuring each distribution, see [Defining connection details in Spark configuration](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/defining-connection-details-spark-configuration).

Information noteNote: A Talend Spark Job is not equivalent to a Spark Job as defined in the Apache Spark documentation; a single Job can generate one or more Spark Jobs depending on how you design it. For more information, see [Apache Spark glossary](https://spark.apache.org/docs/latest/cluster-overview.html#glossary).

When you run the Job, statistics are displayed in the design workspace to indicate the progress of the Spark computations.

The execution information of a Talend Spark Job is logged by the HistoryServer service of the cluster being used. To view this information, open the service web console. The name of the Job in the console is automatically constructed to be ProjectName\_JobName\_JobVersion, for example, LOCALPROJECT\_wordcount\_0.1.