I don't think this makes sense. First the article mentions it's for a "non-technical audience" and then the first step ("1. Start with a diagram") is a detailed architecture diagram that nobody will care about or be able to relate to.
If you really want to do a demo you should focus on how it helps the business and not how it works.
This could be showing a detail in the UI the non-technical audience is familiar with like a "Generate report" button that they use daily and is frustratingly slow. You can show a graph of the average waiting time going down.
This could also be an overview over how the page speed improved or how your core web vitals are all green now, improving your ranking. If you achieved that by optimizing a query, switching databases or rewriting an endpoint doesn't really matter in my opinion.
Of course this, as always, depends on the company, culture and audience. Maybe there's a very technical founder who wants to hear about that, in that case ignore everything I said.
If you really want to do a demo you should focus on how it helps the business and not how it works.
This could be showing a detail in the UI the non-technical audience is familiar with like a "Generate report" button that they use daily and is frustratingly slow. You can show a graph of the average waiting time going down.
This could also be an overview over how the page speed improved or how your core web vitals are all green now, improving your ranking. If you achieved that by optimizing a query, switching databases or rewriting an endpoint doesn't really matter in my opinion.
Of course this, as always, depends on the company, culture and audience. Maybe there's a very technical founder who wants to hear about that, in that case ignore everything I said.