Clean Architecture in Practice (Part 2): Entities, Gateways & more (with Adam Kreitals)

Heard of “clean architecture” but not sure what it looks like in real code? In this episode of SEEK Bytes, Seamus, Will and Adam Kreidels (Head of Engineering, Monetisation & Insights at SEEK) are back for Part 2 of their deep dive – unpacking entities, use cases, gateways, the dependency rule and the famous “onion” diagram in a way any IT pro can apply. This episode's special guest: Adam Kreitals (SEEK Head of Engineering, Monetisation & Insights) In this episode, we explore: • Why “start with the database” slows you down – and how leading with business rules and use cases speeds up delivery. • How entities, use cases and gateways work together – using price, order and discount examples from SEEK to show clean seams between domain and tech. • How clean architecture reduces the cost of change – what good separation of concerns looks like in code, and how to spot when frameworks and APIs are leaking into your core domain. If you’re a software engineer, tech lead, architect, SRE, platform engineer or IT manager who wants code that survives framework swaps, org changes and new requirements – and you liked Part 1 – this Part 2 episode gives you the concrete concepts, terminology and mental models to put clean architecture into practice. 👍 Hit Like if you’ve ever tried to refactor “just one endpoint” and found framework or DB details wired all the way through your business logic 🔔 Subscribe to the SEEK Bytes podcast on YouTube so you never miss a new episode 💬 Drop a comment: Which part of clean architecture – entities, use cases, gateways or the dependency rule – are you most keen to try (or untangle) in your own systems? #SEEKBytes #SEEKTech #CleanArchitecture #SOLID #DomainDrivenDesign #SoftwareArchitecture #LegacyCode #Microservices #DevOps #ITCareers