Skip to main content

Architecting a Continuous Recon Platform | /dev/hack s01e02

Join Adam and dade as they discuss how to think about system architecture, how to design for flexibility without overengineering too much, and how they are going to layout the initial Natlas project. Note from dade: I’m very sorry for my audio quality. You might have noticed that I rearranged the whole office and we used different recording software this time. You know that saying about changing too many variables at once? Well that bit me this time, but we’d already finished recording the whole episode before I knew just how bad it was. It’s fixed for future episodes and I’ve done as much as I know how to make it suck less in this episode. Project Repository: Patreon: Hak5: dade: adam: If you have any questions, comments, concerns, ad hominem attacks, please feel free to email us at 00:00 Open 00:31 Software Architecture Overview 02:40 Getting into the Diagram 04:50 Load balancing 05:20 Monolith vs Microservice 08:10 One-way Doors vs Two-way Doors 10:20 Single Page Applications vs Server Side Rendering 13:25 Progressive Enhancement 14:45 API as an abstraction layer for scan agents 17:00 Content Delivery Networks 18:05 CDN vs Load Balancer placement 20:30 Every decision depends… 21:20 Let’s talk about storage 22:10 Oops, All APIs – Costs of using APIs for everything 25:10 Storing raw data 28:25 Storing references to bulk storage 29:07 Architecture Diagram is ready 29:30 Question for you 29:57 Github 30:08 Submitting feedback 30:22 Patreon 30:28 Outro Hak5 — Cyber Security Education, Inspiration, News & Community since 2005: —–☆—–☆—–☆—–☆—–☆—–☆—–☆—–☆—–☆—–☆ Our Site → Shop → Subscribe → Support → Contact Us → Threat Wire RSS → Threat Wire iTunes → —–☆—–☆—–☆—–☆—–☆—–☆—–☆—–☆—–☆—–☆ ____________________________________________ Founded in 2005, Hak5’s mission is to advance the InfoSec industry. We do this through our award winning educational podcasts, leading pentest gear, and inclusive community – where all hackers belong.