22  Debate: IoT System Design Trade-off Scenarios

Six Worked Architecture, Data, and Business Decision Scenarios

design-methodology
iot
tradeoff
scenarios

Each scenario below presents a realistic IoT engineering decision with competing constraints. Work through the discussion questions before checking your reasoning against the trade-offs raised in each one.

22.1 Monolithic vs Microservices for IoT

Discussion Prompt

Scenario: A startup is building a fleet management platform expected to scale from 100 to 100,000 vehicles over 3 years.

Debate: Start with monolith or microservices?

Consider:

  • Team size and expertise
  • Time to market pressure
  • Operational complexity
  • Scaling requirements

22.2 Time-Series DB vs Traditional SQL

Discussion Prompt

Scenario: An energy company needs to store and query 10 years of smart meter data (15-minute intervals, 1 million meters).

Question: InfluxDB/TimescaleDB or PostgreSQL with proper indexing?

Discussion Points:

  1. Query patterns (recent vs historical)
  2. Compression requirements
  3. Team’s existing expertise
  4. Integration with BI tools

22.3 Open Source vs Proprietary Firmware

Discussion Prompt

Scenario: You’re choosing firmware for a new IoT product line. Budget allows either: - A) Open-source RTOS with community support - B) Commercial RTOS with vendor support contract

Debate the Trade-offs:

  • Security vulnerability response time
  • Long-term maintenance costs
  • Regulatory compliance evidence
  • Talent availability

22.4 Data Monetization Ethics

Discussion Prompt

Scenario: A fitness wearable company has anonymized health data from 10 million users. A pharma company offers $50M for access to study medication adherence patterns.

Question: Should they sell the data?

Positions:

  1. Yes, with consent: Users agreed to terms of service
  2. Yes, anonymized: No individual harm possible
  3. No, trust violation: Users didn’t expect this use
  4. Conditional: Only for beneficial research

Facilitator Note: This has no “right” answer - explore the reasoning.

22.5 Planned Obsolescence in IoT

Discussion Prompt

Scenario: A smart thermostat company must decide end-of-life policy. Hardware works fine but cloud services cost money to maintain.

Options:

  1. End cloud support after 5 years (device becomes “dumb”)
  2. Offer paid extended support subscription
  3. Open-source the cloud backend for self-hosting
  4. Design for 10+ year offline operation from start

Debate: What’s the ethical and business-appropriate approach?

22.6 Battery vs Functionality

Discussion Prompt

Scenario: You’re designing a cattle health monitor (ear tag). Requirements: - 5-year battery life - GPS location (high power) - Temperature sensing (low power) - Heart rate monitoring (medium power)

Budget: Only one CR2032 battery fits the form factor.

Challenge: Which features do you include/exclude? Justify to your team.

22.7 Backward Compatibility

Discussion Prompt

Scenario: Your IoT platform has 50,000 deployed devices using Protocol v1. You’ve designed v2 with major security improvements, but it’s incompatible with v1.

Options:

  1. Force upgrade (break v1 devices)
  2. Maintain both indefinitely
  3. Gateway translation layer
  4. Phase out v1 over 2 years

Debate: What’s the responsible path forward?