Discovering Backend Bottlenecks: Unlocking Peak Performance - Printable Version +- Softwarez.Info - Software's World! (https://softwarez.info) +-- Forum: Library Zone (https://softwarez.info/Forum-Library-Zone) +--- Forum: Video Tutorials (https://softwarez.info/Forum-Video-Tutorials) +--- Thread: Discovering Backend Bottlenecks: Unlocking Peak Performance (/Thread-Discovering-Backend-Bottlenecks-Unlocking-Peak-Performance) |
Discovering Backend Bottlenecks: Unlocking Peak Performance - nieriorefasow63 - 06-20-2023 Discovering Backend Bottlenecks: Unlocking Peak Performance Published 6/2023 Created by Hussein Nasser MP4 | Video: h264, 1280x720 | Audio: AAC, 44.1 KHz, 2 Ch Genre: eLearning | Language: English | Duration: 43 Lectures ( 9h 45m ) | Size: 8.43 GB Harness Chrome DevTools, MITM Proxy, and Wireshark to Pinpoint and Resolve Bottlenecks in Your Backend Stack What you'll learn Identify bottlenecks in backend applications Find where latencies live Intercept slow requests from Mobile and Web Apps Using DevTools Networking tap to its full potentional Using Man in the middle proxy MITM to intercept HTTP requests Using Wireshark for packet inspections Real-world Performance Analysis of Backend Applications Requirements Must have built a frontend or backend application Familiar with networking and backend concepts Description I used to think that performance of the backend depends on the application logic itself. However, there are many other factors that play a role in overall quality and performance of the application. Networking, connection establishment, security, backend communication, protocol serialization, intermediaries and much more.Often debugging the app if you have the source code allows the developer to zone in to the problem and identify it, However most of the time as an engineer you either don't have access to the source code or its time consuming to debug a complex app. That is why in this course I present you with some tools I use to analyze the backend application performance and provide a good guess and what might be the problem without stepping in the code. Often known as black box testing.If your application is a web application that is consumable through a browser, devtools allow us to pretty much inspect all traffic going out from the app and can tell us so much about the app. If the app is not available in the browser we will then demonstrate MITM proxy which is a proxy that intercepts HTTP traffic and log it, this way we can inspect requests and see which of those are the culprit. Finally, if the app uses a protocol that isn't HTTP intercepting it with a proxy becomes little tricky, so we will use both tcpdump and Wireshark to capture low level packets and see our requests this way.This course is designed for developers and engineers who have built backend and frontend applications and would like to take their skills further. This course is intermediate to advanced and it is recommended that students have a background in networking and backend fundamentals both of which I have courses for. Who this course is for Backend Engineers Frontend Engineers Q&A Engineers Full Stack Engineers HOMEPAGE DOWNLOAD |