How to handle entry and storage of location info with Phoenix and Ecto?

I’d go with LiveView if you can. Consider actually running the query only after certain amount of characters were typed in. I would not store the definition of cities/countries in the database - just keep it in memory. If you need to query the data by location, I’d suggest adding an index on a string column.

Thanks!
What would be a more efficient way to store so much data in memory?
i.e. how about performance of querying and validating correctness (inclusion) before saving to DB?

eg. maybe using a Struct with nested keys like:

 %Location{ 
  region(eg. Africa): %{
    country(eg. Egypt): %{
      state_province: [ ... list of cities ]
    }
  } 
}

(not sure if this is the right way to go).

Seems like a pretty common need (in many apps a user or institution may have one or more physical addresses), yet I couldn’t find any published best practices for Elixir/Phoenix.

I don’t want to reinvent the wheel here, so pointers to any libs or articles are welcome!

Many apps have addresses, but I’m not sure how many of those try to validate those given the nature of actual valid addresses being super complex and a list of cities likely being outdated a month after an update.

I made @kip deal with that question for his tzworld library recently. You can have a look here: Tz_world / timezone_boundary_builder update - #5 by LostKobrakai

It’s a tradeoff for access time against space in memory (against space on disk, which you likely have enough of). He used an in memory cache in places to prefilter the list of possible matches completely in memory. Not sure if there’s something like that you could do / or need.

Another option would be using postgres and proper full text search or even elasticsearch. Fuzzy text search requires a lot of details and sometimes one is better of using an existing solution for a problem.

Thanks for the pointers!