Ecto is way more powerful than a simple database wrapper and can fetch and query data from basically any source, you can set up an Ecto.Repo that can fetch/update answers from a json api (or multiple data sources at once) and format/validate it using an Ecto.Schema and your app wouldn’t have any idea that it would be data from an json api and not an DB, because of this the Ecto documentation focus in the most generic abstracted parts, migrations are something pretty much SQL related and they are in their own ecto_sql module, but I agree that for someone that isn’t used to it it can be a bit confusing.
thomas.fortes
0
loon
dimitarvp
Hey, don’t forget that part of the Repo config options that you can supply in your config/**.exs files (only those that pertain to actual DB connections, and they are a lot) are actually documented inside DBConnection.start_link/2. 
2