What are template literals and what can you do with them?
For anything longer than a line or two, template literals are usually the better choice, and the difference is not only about line length. The reason is that concatenation with the plus sign has to be split across many string literals and joined with the operator. That makes the expression hard to read, easy to break in the middle of a word, and it produces a lot of intermediate strings.
A template literal keeps the shape of the text intact. The whitespace, the indentation, and the line breaks are exactly as you typed them, so you can lay out a block of markup or SQL in the source and see it as it will appear at runtime. With concatenation, the layout of the code is dominated by quotes and plus signs, and the text itself is buried.
There is a subtle but important consequence of this. Whitespace inside a template literal is significant, so an indented multiline template will include that indentation in the output. That matters when you are generating markup, and it is the reason that some teams use a helper that strips the common indentation, or a tagged template that removes it for you.
Performance is a reasonable follow-up question. Modern engines optimise both forms well, and for typical string sizes the difference is too small to notice. A template literal can still allocate an intermediate string for every substitution, so for a very hot path that builds large strings inside a loop, an array of parts joined once at the end is often the better pattern.