entityQuery vs. entityTypeManager I have a custom content type user_in_club and I'd like to load a single specific node matching two field values. There are 2 ways (I know of) which can solve this:

$result = \Drupal::entityQuery('node')
-&gt;condition('type', 'user_in_club')
-&gt;condition('field_user_id', $account-&gt;id())
-&gt;condition('field_club_id',$active_club)
-&gt;execute();
$nodes = \Drupal::entityTypeManager()-&gt;getStorage('node')-&gt;loadMultiple($result);


OR

$nodes = \Drupal::entityTypeManager()
-&gt;getStorage('node')
-&gt;loadByProperties(['type' =&gt; 'user_in_club', 'field_user_id' =&gt; $account-&gt;id(), 'field_club_id' =&gt; $active_club ]);


In my single example only one node id is returned, but in case I  have multiple node ids returned, is one method to be preferred over the other in terms of performance etc ? I currently don't see a big difference other than ETQ is better to create more complex queries.
They're identical. loadByProperties() actually converts your conditions to an entity query internally.

I'd acually recommend to do an entity query yourself, directly. It's more readable and loadByProperties() might get deprecated in the future.