From Theory to Practice: Resolve Performance Anti-Patterns with Well-Architected

Подписаться 12 тыс.

Просмотров 1,4 тыс.

50% 1

Learn how to resolve Performance Anti-Patterns using the guidance from the Well-Architected Framework. Go from theory to practice on how to flip Performance Anti-Patterns to Patterns in an LWC application.
Performance (Throughput and Latency) Patterns and Anti-Patterns: architect.salesforce.com/well...
Connect with Salesforce Architects:
Website: architect.salesforce.com/
Twitter: SalesforceArchs?s=20
LinkedIn: / salesforce-architects
00:00 - Intro
00:28 - Explaining Performance and Throughput Anti-Patterns
02:06 - Introduction to Patterns and Anti-Patterns Explorer
03:43 - Starting off demo of Throughput Anti-Patterns in Salesforce
04:19 - Introducing the Anti-Pattern Use Case
05:42 - Running demonstration of Throughput Anti-Patterns in Salesforce
07:40 - Incorrect assumptions about Anti-Patterns
08:35 - Getting counts of how much data is in our object in Code Builder
11:15 - Reviewing the code with Throughput Anti-Patterns in Code Builder
14:23 - Fixed code that contained Throughput Anti-Patterns in Code Builder
16:46 - Seeing out fixed code in action within demo in Salesforce
18:00 - Resolving some Anti-Patterns introduced new Anti-Patterns
19:24 - Introducing Latency Anti-Patterns
20:55 - Introducing Scale Center
21:35 - Reviewing Scale Center Org Performance
21:35 - Finding Performance Anti-Patterns in Scale Center
24:23 - Outro

Наука

Опубликовано:

21 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 2

@tanvirutube 2 месяца назад

I am not sure how the code resolved any performance at all? Actually the use case itself was changed when the code was tweaked, so the results are different which is not the business use case at all. The first code had LIKE statement but never had % appended to it, which is not a normal practice at all in the database world. While the example shows to introduce % for address, but then replaces other fields with = which means that now the search IL that was bringing records where city field were like "Millwalkie" or "Philadelphia" will not come as a result in your search.