j40-tray-snapshot INTRODUCTION The J40-Tray is a food ordering web app designed for the local J40 Restaurant. Our project’s primary goal is to reduce the time customers spend waiting at the restaurant by allowing them to browse the available food online and place orders for pickup, delivery, or dine-in. By improving the ordering experience, J40 Restaurant hopes to enhance its customer service and streamline its operations during peak hours. Team Members and Roles: Emmanuel A. Akalo (Full Stack Developer) This project was completed over a span of six weeks, focusing on delivering a user-friendly platform that serves the needs of both customers and restaurant staff. Who is the Project For?

Postmortem: Web Stack Outage Issue Summary: Duration: August 16, 2024, 10:30 AM - 12:00 PM UTC (1 hour 30 minutes) Impact: The company’s main e-commerce website experienced severe slowdowns, leading to degraded user experience. Approximately 60% of users reported page load times exceeding 30 seconds, resulting in a spike in abandoned carts and failed checkouts. Root Cause: A misconfigured Nginx server update triggered a conflict in load balancing rules, causing a bottleneck in the application’s backend requests. Timeline: 10:30 AM: Monitoring system triggered an alert for high latency across multiple endpoints. 10:32 AM: On-call engineer confirmed the issue and began investigating increased server response times.

istockphoto-1084095896-612x612 Ever typed a web address into your browser and wondered what happens next? It might seem like magic, but there's a complex journey that occurs behind the scenes that delivers the content you see on your screen. Let's delve into the journey a web request takes from the moment you hit enter: Scene 1: The Address Lookup DNS Request: When the user types "https://www.google.com" (the URL), your browser doesn't understand this human-readable format. It needs an IP address, a unique numerical identifier for computers on the internet. So, your browser sends a DNS(Domain Name System) request to a DNS server. The DNS server is like a giant book for the internetk, translating website name (domains) into their corresponding IP addressses. The translating happens through a hierarchical process:a. Local DNS Resolver: Hitting enter does not go striaght to the internet. it first searches the local DNS resolver(provided by your internet service provider). The resolver might have a cache of recently looked up domains and their corresponding IP addresses.If the requested domain is in the cache then the IP address is retrieved and passed on to the browser.b. Recursive vs. Iterative Resolution: if the local resolver doesn't have the IP address, it initiates a recursive or iterative resolution process:Recursive Resolution:(most common approach) The local resolver acts on your behalf, contacting a series of DNS servers until it finds the one that holds the IP address for the requested domain. it involves:Root Nameserver: The local resolver first queries a root nameserver. See this as the internet switchboard with the addresses of all Top-Level Domain (TLD) nameservers(like .com, .org, .net). TLD Nameserver: Based on the TLD in the URL (eg: ".com" for Google), the root nameserver directs the resolver to the appropriate TLD nameserver. Authoritative Nameserver: Finally, the TLD nameserver points the resolver to the authoritative nameserver for the specific domain (eg., Google's nameservers). This server holds the actual IP address for "https://www.google.com".