A view is a named SELECT. Querying it runs the query. It stores no data, so it is always current, and it costs whatever the underlying query costs - a view over a slow join is a slow view, and wrapping it in a name does not make it faster.
Views earn their place in three ways. They hide complexity: a five-table join becomes one name that the rest of the application, and the people writing reports, can use without understanding it. They provide a stable interface: when the tables underneath are reshaped, the view can be rewritten to keep the same columns, and nothing that reads it needs to change. And they restrict access: grant someone SELECT on a view that excludes the salary column and they can query the rest without being able to reach it - which is a real boundary, because they have no privilege on the base table at all.
A simple view - one table, no aggregation, no DISTINCT, no GROUP BY - is updatable, so you can INSERT and UPDATE through it. Add WITH CHECK OPTION and the server also refuses writes that would produce a row the view cannot see, which is otherwise a confusing way to make data disappear.
MySQL has two algorithms. MERGE folds the view into the outer query, which is what you want. TEMPTABLE materialises it first, which blocks index use from outside and is chosen automatically for aggregates and DISTINCT.
-- Hides a join behind one name. Always current; costs what the query costs.
CREATE OR REPLACE VIEW order_summary AS
SELECT o.id,
o.reference,
o.placed_at,
c.name AS customer,
c.city,
SUM(oi.quantity * oi.unit_price) AS total
FROM orders o
JOIN customers c ON c.id = o.customer_id
JOIN order_items oi ON oi.order_id = o.id
GROUP BY o.id, o.reference, o.placed_at, c.name, c.city;
SELECT * FROM order_summary WHERE city = 'London' ORDER BY total DESC;
-- A security boundary: this account gets the view and NOT the table,
-- so the salary column is unreachable rather than merely unselected.
CREATE VIEW staff_directory AS
SELECT id, name, department, extension FROM employees WHERE left_on IS NULL;
-- GRANT SELECT ON shop.staff_directory TO 'reception'@'%';
-- Simple enough to be updatable. CHECK OPTION refuses a write that would
-- produce a row this view cannot see - otherwise rows vanish on save.
CREATE OR REPLACE VIEW active_products AS
SELECT id, name, sku, price FROM products WHERE is_active = TRUE
WITH CHECK OPTION;
UPDATE active_products SET price = 2.50 WHERE sku = 'SKU-00001234';
-- UPDATE active_products SET is_active = FALSE WHERE id = 1; -- refused
SHOW CREATE VIEW order_summary;