/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Amazon's streaming data service, Kinesis, is now available

Kinesis, the streaming data service that Amazon Web Services announced in November, is now publicly available.  The service is comparable in theory to popular open source technologies such as Apache Storm, only Kinesis brings …

Gigaom Derrick Harris

Context & Ripple Effects

Amazon Web Services announced Kinesis, its streaming data service, in November 2013 and has now opened it to all customers — a managed pipe for high-volume event data, positioned against self-operated open source tools like Apache Storm. The pickup was unusually broad for an infrastructure launch: ZDNet, TechCrunch and InfoWorld all ran the story on the day of general availability.

The move fits a decade-long arc at AWS. Back in 2008 Gigaom argued that AWS was no longer just for early adopters, and in 2009 analysts flagged how Amazon's video streaming entry would disrupt the CDN business. Kinesis extends that playbook from static delivery into real-time data processing — taking a workload that previously required running your own distributed cluster and turning it into a line item on an AWS bill.

First-order effects

  • Teams building real-time applications on self-managed Storm-style clusters gain a fully managed alternative inside AWS, removing cluster operations from the critical path of shipping a streaming app.
  • AWS widens its data platform beyond storage and databases into stream ingestion, giving existing AWS customers one fewer reason to run data infrastructure elsewhere.

Second-order effects

  • Open source streaming projects and any vendors commercializing them face pressure to match the managed, pay-per-use consumption model rather than competing on software alone.
  • Enterprises evaluating streaming architectures now weigh operational simplicity on AWS against portability, shifting vendor conversations from 'which framework' toward 'which platform hosts it'.

Third-order effects

  • If the pattern holds, the big-data toolchain — ingestion, processing, analytics — consolidates onto cloud provider menus, with latency-sensitive data handling becoming an on-demand utility rather than a self-operated engineering discipline.
  • The open source ecosystem risks being repositioned as the R&D layer whose innovations are productized by the hyperscalers, changing where value accrues in the streaming stack.

The trend: Cloud providers are steadily absorbing the big-data stack into managed services, converting what used to be self-operated distributed systems into metered platform features.