base on Blazingly fast and light-weight Actor engine written in Golang [](https://goreportcard.com/report/github.com/anthdm/hollywood)  <a href="https://discord.gg/gdwXmXYNTh"> <img src="https://discordapp.com/api/guilds/1025692014903316490/widget.png?style=shield" alt="Discord Shield"/> </a> # Blazingly fast, low latency actors for Golang Hollywood is an ULTRA fast actor engine build for speed and low-latency applications. Think about game servers, advertising brokers, trading engines, etc... It can handle **10 million messages in under 1 second**. ## What is the actor model? The Actor Model is a computational model used to build highly concurrent and distributed systems. It was introduced by Carl Hewitt in 1973 as a way to handle complex systems in a more scalable and fault-tolerant manner. In the Actor Model, the basic building block is an actor, sometimes referred to as a receiver in Hollywood, which is an independent unit of computation that communicates with other actors by exchanging messages. Each actor has its own state and behavior, and can only communicate with other actors by sending messages. This message-passing paradigm allows for a highly decentralized and fault-tolerant system, as actors can continue to operate independently even if other actors fail or become unavailable. Actors can be organized into hierarchies, with higher-level actors supervising and coordinating lower-level actors. This allows for the creation of complex systems that can handle failures and errors in a graceful and predictable way. By using the Actor Model in your application, you can build highly scalable and fault-tolerant systems that can handle a large number of concurrent users and complex interactions. ## Features - Guaranteed message delivery on actor failure (buffer mechanism) - Fire & forget or request & response messaging, or both - High performance dRPC as the transport layer - Optimized proto buffers without reflection - Lightweight and highly customizable - Cluster support for writing distributed self discovering actors # Benchmarks ``` make bench ``` ``` spawned 10 engines spawned 2000 actors per engine Send storm starting, will send for 10s using 20 workers Messages sent per second 3244217 .. Messages sent per second 3387478 Concurrent senders: 20 messages sent 35116641, messages received 35116641 - duration: 10s messages per second: 3511664 deadletters: 0 ``` # Installation ``` go get github.com/anthdm/hollywood/... ``` > Hollywood requires Golang version `1.21` # Quickstart We recommend you start out by writing a few examples that run locally. Running locally is a bit simpler as the compiler is able to figure out the types used. When running remotely, you'll need to provide protobuffer definitions for the compiler. ## Hello world. Let's go through a Hello world message. The complete example is available in the [hello world](examples/helloworld) folder. Let's start in main: ```go engine, err := actor.NewEngine(actor.NewEngineConfig()) ``` This creates a new engine. The engine is the core of Hollywood. It's responsible for spawning actors, sending messages and handling the lifecycle of actors. If Hollywood fails to create the engine it'll return an error. For development you shouldn't use to pass any options to the engine so you can pass nil. We'll look at the options later. Next we'll need to create an actor. These are some times referred to as `Receivers` after the interface they must implement. Let's create a new actor that will print a message when it receives a message. ```go pid := engine.Spawn(newHelloer, "hello") ``` This will cause the engine to spawn an actor with the ID "hello". The actor will be created by the provided function `newHelloer`. Ids must be unique. It will return a pointer to a PID. A PID is a process identifier. It's a unique identifier for the actor. Most of the time you'll use the PID to send messages to the actor. Against remote systems you'll use the ID to send messages, but on local systems you'll mostly use the PID. Let's look at the `newHelloer` function and the actor it returns. ```go type helloer struct{} func newHelloer() actor.Receiver { return &helloer{} } ``` Simple enough. The `newHelloer` function returns a new actor. The actor is a struct that implements the actor.Receiver. Lets look at the `Receive` method. ```go type message struct {} func (h *helloer) Receive(ctx *actor.Context) { switch msg := ctx.Message().(type) { case actor.Initialized: fmt.Println("helloer has initialized") case actor.Started: fmt.Println("helloer has started") case actor.Stopped: fmt.Println("helloer has stopped") case *message: fmt.Println("hello world", msg.data) } } ``` You can see we define a message struct. This is the message we'll send to the actor later. The Receive method also handles a few other messages. These lifecycle messages are sent by the engine to the actor, you'll use these to initialize your actor The engine passes an actor.Context to the `Receive` method. This context contains the message, the PID of the sender and some other dependencies that you can use. Now, lets send a message to the actor. We'll send a `message`, but you can send any type of message you want. The only requirement is that the actor must be able to handle the message. For messages to be able to cross the wire they must be serializable. For protobuf to be able to serialize the message it must be a pointer. Local messages can be of any type. Finally, lets send a message to the actor. ```go engine.Send(pid, "hello world!") ``` This will send a message to the actor. Hollywood will route the message to the correct actor. The actor will then print a message to the console. The **[examples](examples/)** folder is the best place to learn and explore Hollywood further. ## Spawning actors When you spawn an actor you'll need to provide a function that returns a new actor. As the actor is spawn there are a few tunable options you can provide. ### With default configuration ```go e.Spawn(newFoo, "myactorname") ``` ### Passing arguments to the constructor Sometimes you'll want to pass arguments to the actor constructor. This can be done by using a closure. There is an example of this in the [request example](examples/request). Let's look at the code. The default constructor will look something like this: ```go func newNameResponder() actor.Receiver { return &nameResponder{name: "noname"} } ``` To build a new actor with a name you can do the following: ```go func newCustomNameResponder(name string) actor.Producer { return func() actor.Receiver { return &nameResponder{name} } } ``` You can then spawn the actor with the following code: ```go pid := engine.Spawn(newCustomNameResponder("anthony"), "name-responder") ``` ### With custom configuration ```go e.Spawn(newFoo, "myactorname", actor.WithMaxRestarts(4), actor.WithInboxSize(1024 * 2), actor.WithId("bar"), ) ) ``` The options should be pretty self explanatory. You can set the maximum number of restarts, which tells the engine how many times the given actor should be restarted in case of panic, the size of the inbox, which sets a limit on how and unprocessed messages the inbox can hold before it will start to block. ### As a stateless function Actors without state can be spawned as a function, because its quick and simple. ```go e.SpawnFunc(func(c *actor.Context) { switch msg := c.Message().(type) { case actor.Started: fmt.Println("started") _ = msg } }, "foo") ``` ## Remote actors Actors can communicate with each other over the network with the Remote package. This works the same as local actors but "over the wire". Hollywood supports serialization with protobuf. ### Configuration remote.New() takes a listen address and a remote.Config struct. You'll instantiate a new remote with the following code: ```go tlsConfig := TlsConfig: &tls.Config{ Certificates: []tls.Certificate{cert}, } config := remote.NewConfig().WithTLS(tlsConfig) remote := remote.New("0.0.0.0:2222", config) engine, err := actor.NewEngine(actor.NewEngineConfig().WithRemote(remote)) ``` Look at the [Remote actor examples](examples/remote) and the [Chat client & Server](examples/chat) for more information. ## Eventstream In a production system thing will eventually go wrong. Actors will crash, machines will fail, messages will end up in the deadletter queue. You can build software that can handle these events in a graceful and predictable way by using the event stream. The Eventstream is a powerful abstraction that allows you to build flexible and pluggable systems without dependencies. 1. Subscribe any actor to a various list of system events 2. Broadcast your custom events to all subscribers Note that events that are not handled by any actor will be dropped. You should have an actor subscribed to the event stream in order to receive events. As a bare minimum, you'll want to handle `DeadLetterEvent`. If Hollywood fails to deliver a message to an actor it will send a `DeadLetterEvent` to the event stream. Any event that fulfills the `actor.LogEvent` interface will be logged to the default logger, with the severity level, message and the attributes of the event set by the `actor.LogEvent` `log()` method. ### List of internal system events * `actor.ActorInitializedEvent`, an actor has been initialized but did not processed its `actor.Started message` * `actor.ActorStartedEvent`, an actor has started * `actor.ActorStoppedEvent`, an actor has stopped * `actor.DeadLetterEvent`, a message was not delivered to an actor * `actor.ActorRestartedEvent`, an actor has restarted after a crash/panic. * `actor.RemoteUnreachableEvent`, sending a message over the wire to a remote that is not reachable. * `cluster.MemberJoinEvent`, a new member joins the cluster * `cluster.MemberLeaveEvent`, a new member left the cluster * `cluster.ActivationEvent`, a new actor is activated on the cluster * `cluster.DeactivationEvent`, an actor is deactivated on the cluster ### Eventstream example There is a [eventstream monitoring example](examples/eventstream-monitor) which shows you how to use the event stream. It features two actors, one is unstable and will crash every second. The other actor is subscribed to the event stream and maintains a few counters for different events such as crashes, etc. The application will run for a few seconds and the poison the unstable actor. It'll then query the monitor with a request. As actors are floating around inside the engine, this is the way you interact with them. main will then print the result of the query and the application will exit. ## Customizing the Engine We're using the function option pattern. All function options are in the actor package and start their name with "EngineOpt". Currently, the only option is to provide a remote. This is done by ```go r := remote.New(remote.Config{ListenAddr: addr}) engine, err := actor.NewEngine(actor.EngineOptRemote(r)) ``` addr is a string with the format "host:port". ## Middleware You can add custom middleware to your Receivers. This can be useful for storing metrics, saving and loading data for your Receivers on `actor.Started` and `actor.Stopped`. For examples on how to implement custom middleware, check out the middleware folder in the ***[examples](examples/middleware)*** ## Logging Hollywood has some built in logging. It will use the default logger from the `log/slog` package. You can configure the logger to your liking by setting the default logger using `slog.SetDefaultLogger()`. This will allow you to customize the log level, format and output. Please see the `slog` package for more information. Note that some events might be logged to the default logger, such as `DeadLetterEvent` and `ActorStartedEvent` as these events fulfill the `actor.LogEvent` interface. See the Eventstream section above for more information. # Test ``` make test ``` # Community and discussions Join our Discord community with over 2000 members for questions and a nice chat. <br> <a href="https://discord.gg/gdwXmXYNTh"> <img src="https://discordapp.com/api/guilds/1025692014903316490/widget.png?style=banner2" alt="Discord Banner"/> </a> # Used in Production By This project is currently used in production by the following organizations/projects: - [Sensora IoT](https://sensora.io) # License Hollywood is licensed under the MIT licence. ", Assign "at most 3 tags" to the expected json: {"id":"6399","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"