docs/src/main/paradox/create-actors.md - pekko-quickstart-java.g8 - Git at Google

 ## Creating the Actors

 So far we have looked at the definitions of Actors and their messages. Now let's dive a bit deeper into the power of location transparency and see how to create Actor instances.

 ### The power of location transparency

 In Pekko you *can't* create an instance of an Actor using the `new` keyword. Instead, you create Actor instances using a factory `spawn` methods.
 Spawn does not return an actor instance, but a reference, `org.apache.pekko.actor.typed.ActorRef`, that points to the actor instance.
 This level of indirection adds a lot of power and flexibility in a distributed system.

 _In Pekko location doesn't matter_. Location transparency means that the `ActorRef` can, while retaining the same semantics, represent an instance of the running actor in-process or on a remote machine.
 If needed, the runtime can optimize the system by changing an Actor's location or the entire application topology while it is running. This enables the "let it crash" model of failure management in which the system can heal itself by crashing faulty Actors and restarting healthy ones.

 ### The Apache Pekko ActorSystem

 An `ActorSystem` is the initial entry point into Pekko. Usually only one `ActorSystem` is created per application. An `ActorSystem` has a name and a guardian actor. The bootstrap of your application is typically done within the guardian actor.

 The guardian actor of this `ActorSystem` is `GreeterMain`.

 @@snip [GreeterMain.java]($g8src$/java/$package$/PekkoQuickstart.java) { #actor-system }

 It uses `Behaviors.setup` to bootstrap the application.

 @@snip [GreeterMain.java]($g8src$/java/$package$/GreeterMain.java)

 ### Spawning child actors

 Other actors are created using `spawn` methods on `ActorContext`. The `GreeterMain` creates a `Greeter` actor
 this way on startup, as well as a new `GreeterBot` each time it receives a `SayHello` message.


 @@snip [GreeterMain.java]($g8src$/java/$package$/GreeterMain.java) { #create-actors }
	## Creating the Actors

	So far we have looked at the definitions of Actors and their messages. Now let's dive a bit deeper into the power of location transparency and see how to create Actor instances.

	### The power of location transparency

	In Pekko you can't create an instance of an Actor using the `new` keyword. Instead, you create Actor instances using a factory `spawn` methods.
	Spawn does not return an actor instance, but a reference, `org.apache.pekko.actor.typed.ActorRef`, that points to the actor instance.
	This level of indirection adds a lot of power and flexibility in a distributed system.

	_In Pekko location doesn't matter_. Location transparency means that the `ActorRef` can, while retaining the same semantics, represent an instance of the running actor in-process or on a remote machine.
	If needed, the runtime can optimize the system by changing an Actor's location or the entire application topology while it is running. This enables the "let it crash" model of failure management in which the system can heal itself by crashing faulty Actors and restarting healthy ones.

	### The Apache Pekko ActorSystem

	An `ActorSystem` is the initial entry point into Pekko. Usually only one `ActorSystem` is created per application. An `ActorSystem` has a name and a guardian actor. The bootstrap of your application is typically done within the guardian actor.

	The guardian actor of this `ActorSystem` is `GreeterMain`.

	@@snip [GreeterMain.java]($g8src$/java/$package$/PekkoQuickstart.java) { #actor-system }

	It uses `Behaviors.setup` to bootstrap the application.

	@@snip [GreeterMain.java]($g8src$/java/$package$/GreeterMain.java)

	### Spawning child actors

	Other actors are created using `spawn` methods on `ActorContext`. The `GreeterMain` creates a `Greeter` actor
	this way on startup, as well as a new `GreeterBot` each time it receives a `SayHello` message.


	@@snip [GreeterMain.java]($g8src$/java/$package$/GreeterMain.java) { #create-actors }