Here are a couple of questions for you, that might help you:
Are the URLs in the two function clauses the same? If they are, you could extract this out to either another function, or to a module attribute.
Instead of using Kernel.inspect (which is meant to only be used for logging/introspection), you probably want to use to_string, or string interpolation. Also, there is no reason to use Kernel. in front of a function, because the Kernel module is always (unless explicitly overridden) imported into a module.
Why have the get_ in the name of the function? Depending on the context, this might matter for the meaning of the function name but maybe it is fluff that does not add extra meaning.
This is not required. And if you really want to put a verb in there, get is about as vague as you can be, since it means so many different things . Using a verb like get or fetch as part of a function name would make more sense if you retrieve the URL value from somewhere else. In this case, where it is something the function itself calculates, I would just leave it out:
defmodule Team do
def url(team_id) do
Here, it is clear that Team.url(foo) will return an URL based on foo that has to do with a ‘Team’.
Of course, naming things quickly enters the realms of personal preference. It is very easy to spend all afternoon bikeshedding about it. It’s possibly the least important suggestion of all of the suggestions that people have given in this topic .
A follow up question:
I have to an request data from an foreign API for about 1 million times. So for every single team_id I have to contact an url, receive the data and insert (or update) the data as a new row in a database (if it meets certain conditions).
I know I can do this easily via for but wouldn’t that be a perfect fit for GenServer? That would give me a first practise on genserver…