Concert Logistics Management

What Netflix Actually Taught Us About Live Streaming After the Tyson–Paul live event exposed some very public cracks, Netflix did something unusually useful: it published a five-part technical breakdown of how it built live streaming at scale. This article on the Streaming Learning Center summarizes the key lessons from each post and highlights what’s reusable at a scale well below Netflix's. Behind the Streams: Live at Netflix: How Netflix rebuilt its control plane to survive massive, synchronized play storms, handling millions of simultaneous session requests without cascading retries or metadata failures. Building a Reliable Cloud Live Streaming Pipeline: A detailed look at cloud-based ingest, redundancy, and encoding pipelines, and how Netflix replaced traditional broadcast infrastructure with automated cloud workflows. Real-Time Recommendations for Live Events: Why live events break traditional caching and recommendation systems, and how Netflix combined prefetching with broadcast triggers to update over 100 million devices without melting backend services. Netflix Live Origin: An inside look at the custom live origin layer that decouples publishing from read storms, isolates failures, and keeps latency predictable under extreme concurrency. Building a Robust Ads Event Processing Pipeline: How Netflix scaled ad telemetry, metadata, and billing signals for live and VOD without overwhelming devices or downstream systems. Even if your service volume never approaches Netflix traffic levels, the architectural patterns around surge control, observability, and failure isolation still apply.

This week's sketch note is about designing a smart vehicle parking platform. Imagine you are driving on a busy street, looking for a parking spot. With a few taps on your car's infotainment system, you will find a car park nearby, optionally reserving a parking lot before arrival. Yes, such technology exists today in latest vehicle makes, such as Mercedez, BMW, Kia, etc. How would we design a solution like that? To achieve that, car parks should be equipped with a specialized hardware/software module that detects the occupancy status of a given parking lot in real-time, whether occupied or vacant. Once detected, the Event Adapter software component translates that into an Event and publishes it into a topic in a streaming data platform, such as Apache Kafka, Redpanda, Pulsar, etc. The streaming data platform acts as a durable pub-sub broker here, ingesting events from car park modules in real time and making them accessible for downstream processing. Incoming events can be parking lot occupancy changes, lot reservations, and payments made upon exiting. Operational Microservices applications consume these events in real time and update a primary cache, such as Redis, reflecting the current status of the car park occupancy. Parallel to that, events are fed to a data warehouse for running analytics and powering various reporting dashboards. When a driver searches for available parking spaces, those queries first hit the manufacturer's OEM platform and are routed to the nearest parking management platform. Queries from the OEM solution enter the parking management system through an API gateway, which provides security, rate limiting, and protocol translation. The search request finally reaches the Microservices layer, causing them to respond by querying the cache. The response typically contains the number of free lots available. This is a very high-level design that I came up with. But you can use this as a baseline to build more detailed architecture. #dataanalytics #streamingdata #smartparking #systemdesign

The 365-Day Asset Modern stadiums are essentially 5-Star Hotels without bedrooms. 🏨 They have industrial kitchens, auditoriums, and tech infrastructure. Yet, most sit empty 300 days a year. The most overlooked revenue stream in the "Mega Event" economy isn't ticket sales. It is the MICE Sector (Meetings, Incentives, Conferences, Exhibitions). 💼📊 💡 The Blueprint: Real Madrid's "Hypogeum" Revolution Real Madrid didn't just renovate the Bernabéu to seat more fans. They renovated it to monetize Tuesdays. They built a 30-meter deep underground greenhouse (The Hypogeum). It stores the grass in 6 trays with LED lighting and humidity control, leaving a concrete floor above that can handle heavy industrial loads. This engineering masterpiece allows for a "365-Day Revenue" schedule: ✅ Tuesday: Tech Conference or Trade Show. ✅ Thursday: Taylor Swift Concert (VIP Hospitality). ✅ Saturday: La Liga Match (Pitch returns perfect). The Target: €400 Million in non-matchday revenue annually. The Lesson for Saudi Arabia Smart venue operators in the Kingdom must realize their competition isn't just Al-Hilal or Al-Nassr. Your competition is the Ritz-Carlton and the Four Seasons. If you are building a stadium for the 2034 World Cup, you need to be selling your lounges to corporate clients for board meetings on Wednesday mornings. If your stadium is empty from 9:00 AM to 5:00 PM on weekdays, you are leaving millions on the table. A venue must work for the Corporate World on Monday if it wants to afford the Sports World on Saturday. #MICE #RealMadrid #Bernabeu #SportsBiz #SaudiVision2030 #Hospitality #Strategy

Every chaotic show has a pattern. Here’s mine. 12 brutal lessons from 35 years. Managing major events or teams? I’ve learned a lot, mostly by screwing it up first. Here are 12 face-palm moments that taught me the hard way: 1. Assuming everyone knows what's in your head. ↳ Turns out telepathy isn’t listed on anyone’s CV. ↳ Not briefing teams is a major leadership flaw, and I learned this the hard way. 2. Not double-checking schedule dates before confirming vendors. ↳ Nothing like vendors arriving exactly one week early. ↳ If you’re reusing last year’s schedule, triple-check everything. 3. Letting the intern manage the VIP door list. ↳ “Wait, who exactly is Sir Richard Branson?” (True story.) ↳ In my defence, the person assigned the role called in sick. 4. Believing coffee and energy drinks replace sleep. ↳ You might feel immortal, until you definitely don’t. ↳ Nothing replaces good food and rest when you're in the thick of it. 5. Saying 'yes' to every client request without checking reality. ↳ Everything’s possible, until you're sourcing miracles at 2am. ↳ Saying no is a lot more powerful than we think. 6. Exceeding venue capacity restrictions. ↳ "The fire marshal’s here" is a phrase that never ends well. ↳ I’ve worked with a lot of promoters over the years with very large guest lists. 7. Underestimating crew food (and beer) consumption. ↳ Hangry thirsty crews scare me more than severe weather forecasts. ↳ An army marches on its stomach, for real. 8. Trusting spreadsheets are foolproof. ↳ Excel formulas lie when you’re tired, trust me. ↳ No matter how much time you put into making it foolproof, someone will always prove you wrong. 9. Not clearly assigning responsibilities. ↳ "Someone" usually means "no one." ↳ It’s critical to be crystal clear about every single task. 10. Thinking professionals don’t need detailed briefings. ↳ "They’ll figure it out" is officially the worst event strategy. ↳ Professionals thrive on information, you can never give them enough. 11. Ignoring red flags with vendors or team members. ↳ Spoiler: "It’ll be fine" rarely ever is. ↳ As the saying goes, hire slow and fire fast. 12. Not having a designated troubleshooter. ↳ When things go sideways, you need someone whose only job is "fix things." ↳ This became one of the most valuable positions I ever employed. The difference between chaos and control? It’s almost always planning. Which one of these have you done, or dodged, on your shows? (Brave enough to add number 13?) --- 🔔 Follow Iain Morrison for blunt truths about how real events run ♻️ Repost to help someone avoid learning it the hard way 📬 Want more no-fluff lessons from the field? Sign up here: https://lnkd.in/g2c6wTjC

Live browser updates without polling or WebSockets?! Modern applications need live data. Dashboards, monitoring panels, IoT feeds, price tickers. Users expect updates instantly, not every 5 seconds. ✅ Server Sent Events (SSE) solve this cleanly when data flows only from server to client. With ASP .NET Core 10, SSE now has first class support, making real time streaming simple, reliable, and production ready. ✔️ SSE keeps a single HTTP connection open and continuously pushes updates using the text/event-stream format. Browsers consume it natively via EventSource. If the connection drops, the browser reconnects automatically and sends Last-Event-ID. Your API can read it from HttpRequest.Headers and resume the stream without losing events. No manual retry logic. No state juggling on the client. ASP .NET Core 10 introduces below built in primitives: • IAsyncEnumerable<T> for streaming data • SseItem<T> for strongly typed events with IDs and event names • TypedResults.ServerSentEvents for minimal API endpoints • System.Net.ServerSentEvents namespace for native SSE support • EnumeratorCancellation for correct stream cancellation handling This lets you build long lived streaming endpoints with minimal configuration and clear intent. Typical backend flow includes: 1. A singleton service generates events continuously. 2. Each event has an ID, payload, and timestamp. 3. The SSE endpoint maps events into SseItem<T> and streams them to the client. 4. On reconnect, the server resumes from the last event ID automatically. And frontend flow includes: 1. The browser subscribes using EventSource. 2. Events arrive instantly. 3. Reconnections happen automatically. 4. Last-Event-ID is handled for you. No extra libraries. No complex client state. SSE is ideal for: • Dashboards and monitoring • Log and event streaming • Notifications • Stock and price updates • IoT telemetry It works over standard HTTP, scales well, and is easy to secure. ⚠️ Use SSE when communication is one way from server to client. Use SignalR when you need bi directional messaging. SSE is lighter, simpler, and often the better default. P.S. ASP .NET Core 10 makes real time streaming simple, and Server Sent Events are the easiest way to deliver live updates without polling or WebSocket complexity. ♻️ Share this with your network to spread knowledge. ➕ Follow [ Elliot One ] for daily modern engineering insights.

For those already using Bedrock AgentCore Runtime and wondering "but what about real-time voice agents or live streaming?", this one's for you! AgentCore Runtime supports 𝗯𝗶𝗱𝗶𝗿𝗲𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘀𝘁𝗿𝗲𝗮𝗺𝗶𝗻𝗴, and understanding it is simpler than you think! The easiest way to understand it? Two analogies: 📻 𝗛𝗧𝗧𝗣 (𝗗𝗲𝗳𝗮𝘂𝗹𝘁 𝗺𝗼𝗱𝗲) = Walkie-talkie You talk, wait, then the other person talks back. 📞 𝗪𝗲𝗯𝗦𝗼𝗰𝗸𝗲𝘁 (𝗕𝗶𝗱𝗶𝗿𝗲𝗰𝘁𝗶𝗼𝗻𝗮𝗹) = Phone call Both sides talk at the same time, in real-time, and you can interrupt :D Here's how to get started: 1️⃣ Build your agent locally using the @app.websocket decorator (𝘆𝗼𝘂𝗿 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝘄𝗶𝗹𝗹 𝗻𝗲𝗲𝗱 /𝘄𝘀 𝗼𝗻 𝗽𝗼𝗿𝘁 𝟴𝟬𝟴𝟬!) 2️⃣ Test locally: Spin up your agent, connect a WebSocket client, see it work instantly 3️⃣ Deploy with agentcore launch: Same simple flow you already know 4️⃣ Connect via WSS with your choice of auth: SigV4 headers, pre-signed URL, or OAuth 2.0 5️⃣ Stream data both ways in real-time and watch the magic happen 🪄 𝗪𝗵𝗲𝗻 𝘁𝗼 𝘂𝘀𝗲 𝗶𝘁? - Real-time voice conversations with immediate audio streaming - Bidirectional audio/text/binary data flow - Users interrupting the agent mid-response (finally screaming “I want to speak to a person!” will make sense) 𝗪𝗵𝗲𝗻 𝘁𝗼 𝘀𝘁𝗶𝗰𝗸 𝘄𝗶𝘁𝗵 𝗛𝗧𝗧𝗣? Simple request → response patterns without streaming needs Your agents just got a whole lot more conversational! 🚀 Read more about it in this blog by Lana Zhang, Phelipe Fabres and Evandro Franco: https://lnkd.in/gxru5urY #AWS #BedrockAgentCore #AgenticAI #WebSocket #RealtimeAI

An uncomfortable lesson I learned early on when hosting exec or team sessions: The space can absolutely make or kill the vibe. The room you choose for your offsite is already facilitating before you even start. Walk into a formal boardroom with a long table and everyone immediately sits up straighter. They act professional and their language becomes more careful. Walk into a space with comfortable seating, natural light, and flexible layout? People relax, lean in and are more willing to be honest. Architectural and design elements can make you feel entirely different in different spaces. The space you choose is communicating to your team: • “This is formal” or “this is collaborative.” • “Be careful here” or “you can be human here.” To get the best outcomes from your gathering, approach your room setup with as much creative thought as possible. This means asking: → What is this venue communicating to the team before we even start? → Will this space support the conversations we need to have? → Does the layout allow for different types of sessions? → How does the seating setup create: 1. A listening, absorbing audience 2. An engaged discussion 3. An interactive multi-team collaboration The seating arrangement alone can change everything. Your space is doing half of the work of facilitation, either supporting what you’re creating or fighting against it. This is why I ALWAYS recommend teams to get help when booking a venue for their offsite. When I vet venues, I ask the questions most people don’t know to ask: → What are the noise restrictions? (Some venues have strict cutoffs that kill evening sessions) → How's the wifi, really? (I need speed tests, not marketing promises) → Can we rearrange the furniture? (Flexibility matters more than most people realize) → What's the actual cancellation policy for accommodation? And so much more. After 100+ offsites, I know which venues deliver what they promise and which ones oversell. I have a little black book of venues which I know have spaces that support vulnerability and which ones create barriers. I can help you with the questions to ask that prevent day-of disasters. So, if you’re planning an offsite and need help booking a venue: ➡️ Think about what you’re trying to create, then find a space that actually supports it. ➡️ Or, let me help you find one! DM me or email maya@momentumprocesses.com for help finding appropriate offsite venues in the UK and Portugal. What's the worst venue mistake you've made (or seen)? ♻️ Share with someone about to book an offsite venue  ➕ Follow Maya Knight for more on designing offsites that actually work

The feasibility study TSC carried out for a dedicated London Lions basketball arena reinforced two critical lessons that are highly relevant for the Middle East, particularly the GCC. 𝐅𝐢𝐫𝐬𝐭, 𝐝𝐞𝐦𝐚𝐧𝐝 𝐢𝐬 𝐫𝐚𝐫𝐞𝐥𝐲 𝐭𝐡𝐞 𝐩𝐫𝐨𝐛𝐥𝐞𝐦 — 𝐨𝐫𝐜𝐡𝐞𝐬𝐭𝐫𝐚𝐭𝐢𝐨𝐧 𝐢𝐬. The real value in arena planning lies in getting the content mix right: balancing elite sport requirements, anchor IPs, promoter needs, and public policy objectives. This is what determines whether a new arena expands the entertainment ecosystem or simply cannibalises existing supply. In the GCC, where indoor arenas remain relatively scarce but multiple new venues are now in the pipeline, this challenge is amplified. With several arenas coming online in Riyadh alone, long-term success will depend less on raw demand and more on: Securing anchor sports IPs that deliver guaranteed fan demand Programming a year-round, diversified content calendar (sport, entertainment, esports, community, cultural events) Designing venues that are operationally flexible and commercially scalable from day one 𝐒𝐞𝐜𝐨𝐧𝐝, 𝐰𝐞 𝐚𝐫𝐞 𝐬𝐞𝐞𝐢𝐧𝐠 𝐚 𝐠𝐥𝐨𝐛𝐚𝐥 𝐬𝐡𝐢𝐟𝐭 𝐭𝐨𝐰𝐚𝐫𝐝 𝐧𝐞𝐱𝐭-𝐠𝐞𝐧𝐞𝐫𝐚𝐭𝐢𝐨𝐧, 𝐬𝐩𝐨𝐫𝐭-𝐥𝐞𝐝 𝐚𝐫𝐞𝐧𝐚 𝐦𝐨𝐝𝐞𝐥𝐬 — 𝐚𝐧𝐝 𝐭𝐡𝐞 𝐆𝐂𝐂 𝐢𝐬 𝐞𝐧𝐭𝐞𝐫𝐢𝐧𝐠 𝐭𝐡𝐢𝐬 𝐩𝐡𝐚𝐬𝐞 𝐟𝐚𝐬𝐭. Venues such as Manchester’s Co-op Live and Milan’s Santa Giulia Arena illustrate how mature markets continue to invest in arenas not to add capacity, but to upgrade quality, sustainability, technology integration, and revenue performance. Global best practice points to a few non-negotiables: 1) Regularly re-testing feasibility studies as market conditions, event calendars, and competing supply evolve 2) Robust demand and content appraisal, not just headline capacity modelling 3) Early diversification of revenue streams beyond ticketing: premium hospitality, naming rights, F&B concepts, non-event utilisation, digital and data-led monetisation 4) Clear positioning within a city-wide and national events strategy, ensuring each arena has a defined role rather than competing for the same content For the GCC — and Riyadh in particular — the next wave of arena success will be determined by how intelligently venues are differentiated, programmed, and commercialised, not by how fast they are built. 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗶𝘀 𝘁𝗵𝗲 𝗲𝗮𝘀𝘆 𝗽𝗮𝗿𝘁. 𝗦𝘂𝘀𝘁𝗮𝗶𝗻𝗮𝗯𝗹𝗲 𝗱𝗲𝗺𝗮𝗻𝗱 𝗶𝘀 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗱. Get the full analysis in The Sports Consultancy’s Take Five newsletter – plus our view on Premier Padel’s growth trajectory, female sports media after Sky Sports’ TikTok fail, the risks and rewards of US sports’ betting strategy, and the threat Christmas fixture congestion poses to football’s Premier League product quality.    https://lnkd.in/dT5FPhsv

"Who planned this event?" That was the question — delivered by an attendee making his way down the hall in his wheelchair, clearly frustrated. "I did, sir. How can I help?" And in that moment, I knew. We had let this guy down. We had chosen a beautiful, historic venue — the Lumber Exchange Building, a stunning 1885 skyscraper full of vintage charm. It is the oldest high-rise building standing in Minneapolis and the oldest building outside of New York City, with 12 or more floors. It was unique, visually striking, and exactly what the client wanted: something outside of the typical hotel ballroom IN the city that their Foundation represented. But a beautiful venue doesn’t always mean an easy experience for every guest. I had navigated the parking ramp, the pathways with stairs, and even the tricky old elevators myself on my site visit. But what I hadn’t done was fully consider the end-to-end experience of our mobility-challenged guests. While there was ADA parking, we could have done a much better job communicating how best to get from the ADA parking to the event space. Or, better yet, we could have arranged for a greeter to meet this guest and assist with the elevator that was hard to turn a wheelchair around in. While 150 other guests had a great experience, one didn’t, and that matters. With every event, you learn something. And this was a hard lesson that I still think about today. I never want anyone to have a less-than-stellar experience at one of my events. It was a powerful reminder that great events aren’t just about stunning venues or perfect logistics. You must ensure every single guest has a seamless experience. 🔎 What to Consider When Choosing a Venue: 1️⃣ Accessibility Matters – Can all guests navigate the space easily? Are elevators, ramps, and parking clearly marked? Can a wheelchair or scooter easily turn around in the elevator to access the buttons?  2️⃣ Location & Logistics – Is it convenient? Are there transportation and parking options? 3️⃣ Clear Communication – Have you provided detailed instructions on parking, entrances, and mobility options, as well as the easiest route to the event space? 4️⃣ On-Site Support – Would a greeter or dedicated staff member help ease challenges for certain guests? Are you asking the right questions to find out who might need assistance in the Registration platform? 5️⃣ Match the Event’s Purpose – The space should enhance the event’s goals, not just look great in photos. Great events create lasting memories — for the right reasons. If you need help sourcing a venue that works for everyone, we’ve got you covered. Let’s talk! Link to book an appointment in the comments. 📩 #EventPlanning #AccessibilityMatters #WendyPorterEvents #IgniteEventMagic

65 million viewers tuned in, but 500,000 viewers were stuck at the loading screen! Turning Netflix's Mike Tyson-Jake Paul fight stream into a cautionary tale of live streaming failure. For a platform that pioneered chaos engineering, this wasn't just unexpected, it was ironic. So, what went wrong? And more importantly, how can platforms ensure seamless live streaming for massive audiences? 1/ Infrastructure Misalignment ✅ Issue: Netflix’s architecture is optimized for on-demand, not live concurrent traffic. ✅ Challenges: Difficulty in managing real-time data flow and spikes in simultaneous connections. ✅ Solution: Adopt a dual-optimized architecture for live and on-demand streaming. 2/ Content Delivery Network (CDN) Bottlenecks ✅ Issue: Netflix’s proprietary CDN, Open Connect, struggled to handle unexpected peak traffic. ✅ Challenges: Cache exhaustion and limited fallback options during surges. ✅ Solution: Incorporate geo-distributed CDNs with real-time load balancing. 3/ Peering Network Constraints ✅ Issue: Traffic spikes overwhelmed inter-network connections. ✅ Challenges: Bottlenecks in data transfer, leading to lags and errors. ✅ Solution: Build redundancy into network pathways and optimize peering agreements. 4/ Lack of Real-Time Observability ✅ Issue: Limited insight into live traffic patterns and system bottlenecks. ✅ Challenges: Delayed response to issues as they arise. ✅ Solution: Use real-time monitoring tools and predictive analytics to anticipate traffic surges. 5/ Viewer Experience at Risk ✅ Issue: Live streaming lags don’t just frustrate viewers—they damage trust. ✅ Challenges: Missed key moments, broken trust in the platform’s reliability. ✅ Solution: Conduct stress tests under real-world conditions to ensure readiness. The takeaway? Live streaming isn’t just an extension of traditional video delivery. It’s a technical challenge requiring precision, foresight, and the ability to adapt in real-time. BTW enjoy the turkey, the tech, and the time with loved ones—Happy Thanksgiving! _____________________ PS: Don’t forget to visit my profile, Hiren, and subscribe to my weekly newsletter for: - Product engineering insights - Proven development strategies - The latest trends in Azure & Generative AI #Netflix #CDN #StreamingFailures #CloudInfrastructure #Simform