Community Comment: Part 7 - Architects should never evaluate options in a vacuum

The comments I provided in reaction to a community discussion thread.

Managing Director at Educational Institution: Companies are trying to make the decision between building their next-generation pub/sub systems on Pulsar or Kafka. I’ve written a post pulling my real-world experience helping companies make these decisions.
Comparing Pulsar and Kafka From a CTO’s Point of View: How a CTO would make the decision between Kafka and Pulsar
https://dzone.com/articles/comparing-pulsar-and-kafka-from-a-ctos-point-of-vi

Gfesser: Nice write-up. A brief comment on your first paragraph: "When upper management assesses a new technology, they view it from a different perspective than middle management, architects, or data engineers. Upper management is not just looking at benchmarks and feature lists; they’re looking for long-term viability and how it gives their company a clear competitive edge. In addition, they’re optimizing for time to market and costs." Architects should never evaluate options in a vacuum: evaluating near-term and long-term viability in relationship to other factors such as time-to-market and cost is typically the responsibility of the architect.