DEV Community

Robson Tenório
Robson Tenório

Posted on

Our way: Actions vs Services

👉 Go to Summary

There is no wrong or right way, there is our way.

-- Someone

.
.
.

Actions

  1. It represents an internal app use case.
  2. Each action must contain one use case.
  3. Naming is important.
  4. An action can call another action or service in complex scenarios. 

class MakeUserAvatarAction {

    function __construct(){ 
        // ... 
    }

    function execute(){
        // It does only 1 thing
    }    
}
Enter fullscreen mode Exit fullscreen mode

Services

  1. It represents external integrations, commonly through API.
  2. You can have many methods. 
class KeycloakService{

    function __construct(){ 
        // ... 
    }

    function createUser() { }

    function syncRoles() { }

    ...
}
Enter fullscreen mode Exit fullscreen mode

Actions vs Services

  1. An action has one method, that solves one internal use case.
  2. An service can have more methods, that represents an external integration. 
app/
    |
    |__ Actions/    
    |   |   
    |   |__ post/
    |   |   |
    |   |   |__ DeletePostAction.php
    |   |   |__ PromotePostAction.php
    |   |
    |   |__ users/
    |       |
    |       |__ MakeAvatarAction.php
    |
    |__ Services/
        |
        |__ PaymentService.php
        |__ KeycloackService.php
Enter fullscreen mode Exit fullscreen mode

Top comments (0)

Read next

edwin_lisowski profile image

ContextCheck: An open-source framework for testing and evaluating LLMs, RAGs, Chatbots

Edwin Lisowski -

edgaremmanuel profile image

Patterns of Enterprise Application Architecture-Day 2

DevByJESUS -

sunnat_qayumov profile image

HackerRank Problem#13

Sunnat Qayumov -

pentest_testing_corp profile image

Insecure Direct Object References (IDOR) in Laravel

Pentest Testing Corp -