Views vs Materialize Vs Materialized View in Kusto

Scenario: Data in kusto table is updated after 5 hours. Task: Call query from .net API In query , create a subquery and use that subquery to perform join on a bigger table

let table1=materialize(
Customer|where CustomerId=="cust-reg-aabb-cc232"|distinct CustomerId,City);
CustomerPurchase
|where CustomerId=="cust-reg-aabb-cc232"
//perform join with table1 and other things

or

let table1=view(){
Customer|where CustomerId=="cust-reg-aabb-cc232"|distinct CustomerId,City};
CustomerPurchase
|where CustomerId=="cust-reg-aabb-cc232"
//perform join with table1 and CustomerPurchase

CustomerPurchase and Customer data is being updated after every 5 hours(new rows being added). What is more optimized : create a view or use the materialize method. I went through the documentation but could not understand the different between both.

Also since I am implementing an API, is it possible to use materialized view instead of table1?