GetAnalyst Podcast

Real systems.
Real decisions.

Deep, practical conversations for systems analysts, business analysts, and solution architects. Episodes are in Russian; English summaries and translated chapters are provided below.

Latest releases

Cover of GetAnalyst podcast episode 52
Episode 521h 32m

Async Integration with Webhooks and Message Brokers

Design an integration with an AI video service through three architecture options: a monolith without a broker, a monolith with RabbitMQ, and a microservice solution. Includes failure scenarios and development-task decomposition.

English chapter timestamps
  • Intro
  • The scenario and speaker introduction
  • Middle+ async integration task: requirements, API, and mockups
  • How to begin a real integration task
  • AI video service API documentation
  • Synchronous vs. asynchronous: polling and webhooks
  • Message-broker integration: RabbitMQ and Kafka
  • Reading the API documentation, continued
  • Designing the async integration architecture
  • Option 1: monolith without a broker
  • Option 2: monolith with RabbitMQ
  • Option 3: microservice architecture
  • When a webhook never arrives: retries and safeguards
  • Canceling an asynchronous process
  • Errors, stalled jobs, and difficult scenarios
  • Decomposing the solution into development tasks
  • Takeaways, materials, and recommendations
Cover of GetAnalyst podcast episode 51
Episode 5135m

Vibe Coding for Systems Analysts: Building an App with AI

A real case study of an analyst-built AI tool for database design and SQL. See the app, development stack, prompts, token costs, delivery time, and where AI code generation meets engineering.

English chapter timestamps
  • Building an AI database and SQL tool through vibe coding
  • From law to systems analysis: meet the guest
  • Technology stack and product idea
  • Product demo and onboarding
  • Application registration
  • Designing an ER diagram from requirements
  • Analyzing an existing database from DDL or an ER diagram
  • AI-assisted database audit
  • Migrating data between database systems
  • Generating database test data
  • Admin panel, analytics, and token usage
  • System and user prompts
  • Exporting AI-generated reports
  • Ideas for developing the tool
  • Who owns AI-generated code?
  • Do systems analysts need to code?
  • How vibe coding may affect an analyst’s career
  • Development time and key challenges
  • How analysts can start working with AI and vibe coding
Cover of GetAnalyst podcast episode 50
Episode 5058m

How to Build an AI Skill in ChatGPT and Claude

Learn how reusable AI Skills differ from prompts and projects, what goes inside a skill, and how to create one for a systems-integration use case.

English chapter timestamps
  • AI Skills for systems and business analysts
  • Why ordinary prompts are no longer enough
  • What AI Skills are and why they matter
  • REST API requirements example
  • Working before and after Skills
  • What an AI Skill contains
  • UML and REST API skill structures
  • Why analysts need AI Skills
  • Analyst tasks worth automating
  • Using Skills in ChatGPT
  • Creating Skills in ChatGPT
  • AI Projects as a free alternative
  • Combining Projects and Skills
  • Skills in Claude
  • Skills in Perplexity
  • Free access vs. paid plans
  • Creating a Skill from your knowledge
  • Demo: integration use-case Skill in Claude
  • Using AI safely at work
  • Final Skill structure
  • Moving Skills between tools
  • Five steps from creation to use
  • Limitations of Skills
  • Skill, Project, MCP, and Tool: the differences
  • Takeaways and recommendations
Cover of GetAnalyst podcast episode 49
Episode 4923m

Why Your RabbitMQ Will Fail: A Production Incident

A message queue looks empty while the RabbitMQ node is drowning in data. This post-incident analysis explains how delayed personalized emails turned the broker into an object store.

English chapter timestamps
  • Intro
  • Introduction and guest
  • Why RabbitMQ was selected
  • External-system integrations through a broker
  • Delayed Message Exchange: the failure-triggering task
  • Warning signs in logs and monitoring
  • Incident impact and message loss
  • What belongs in a RabbitMQ payload
  • What to do after a broker failure
  • RabbitMQ tools for analysts
  • RabbitMQ infrastructure and nodes
  • Integration design recommendations
Cover of GetAnalyst podcast episode 48
Episode 4836m

Monitoring Metrics for Systems Analysts

Connect measurable non-functional requirements with RPS, CPU, broker metrics, SLI, SLO, SLA, and Google SRE’s four golden signals.

English chapter timestamps
  • Introduction
  • Why analysts need monitoring metrics
  • What monitoring metrics are
  • Non-functional requirements that affect monitoring
  • The analyst’s workflow for defining metrics
  • Key metrics and their data sources
  • Detailed review of each metric
  • CPU load and peak-load requirements
  • Message-broker monitoring metrics
  • SLI, SLO, and SLA
  • Prometheus, Grafana, and Kibana on a real project
  • Google SRE’s four golden signals
  • Summary and checklist

Full archive

More interviews, technical cases, and architecture breakdowns.

Browse all episodes