search

bullseye-arrowEvent Driven

Highly customizable event driven strategy

hashtag
In One Line

Events without tears, signals without fears.

hashtag
Package Info

display name

AceLand Event Driven

package name

latest version

2.3.3

namespace

git repository

https://github.com/parsue/com.aceland.eventdriven.gitarrow-up-right

dependencies

There is two parts in this package:

Event Bus

Signal

hashtag
Usage Patterns

hashtag
Two Complementary Event Systems

The package provides two distinct event management approaches, each optimized for different architectural layers of your application.

hashtag
Event Bus - System Architecture Level

Event Bus serves as a global service discovery and communication system, ideal for:

  • Core Systems Integration

  • Service Layer Communication

  • Cross-Module Operations

  • Global State Management

Best suited for foundational architecture where services need to communicate without direct references, maintaining loose coupling at the system level.

hashtag
Signal - Component Level

Signals provide focused, object-based event management, perfect for:

  • UI Event Handling

  • Component Communication

  • Game Object Interactions

  • Feature-Specific Events

  • Local State Updates

Optimal for higher-level development where specific objects or features need their own event scope.

hashtag
Choosing the Right Approach

hashtag
Use Event Bus when:

  • You need system-wide service communication

  • Working with dependency injection patterns

  • Implementing service locator patterns

  • Building core architecture features

  • Managing global state changes

hashtag
Use Signals when:

  • Handling UI interactions

  • Managing component-specific events

  • Implementing feature-specific messaging

  • Dealing with localized state changes

  • Building self-contained systems

While both systems can be used interchangeably, following these patterns will result in cleaner, more maintainable architecture.

PreviousChange LogNextChange Log

Last updated