Amazon opens Redshift data warehouse to Joe Public

Traditional IT companies nervously stare at ground


Amazon's Redshift cloudy data warehousing service is now available for general consumption after a trial among blessed customers.

The pay-as-you-go technology, which scales from around 200GB into the petabyte range, represents a direct threat to the warehousing divisions of IBM, Oracle, Teradata, and EMC (Greenplum).

Redshift does "10 times the performance at 1/10th the cost of the on-premises data warehouses that are commonly used today," the company wrote in a blog post announcing the service's availability on Friday.

Its architecture is based around columnar data storage, advanced compression, and fast disk and network I/O.

This, combined with its roots in the open source PostgreSQL database, has prompted The Reg to speculate that Amazon has managed to parallelize the PostgreSQL technology.

The warehouse dovetails into other major AWS components, like the S3 storage cloud and DynamoDB. It can suck in data from Amazon RDS, Elastic MapReduce and data sources in EC2 instances via the the recently-launched AWS Data Pipeline.

Pricing for the service can go to as low as $999 per year per terabyte, if using three-year reserved instances. As is typical, the service will initially be run out of Amazon's main data center – US East in Northern Virginia – with expansion occurring around the world "in the coming months."

The service was announced back in November at Amazon's inaugural cloud conference, AWS re:invent.

Redshift is designed to appeal to companies that either don't have the cash to pay for pricey hardware and software from typical warehousing stalwarts like IBM, Oracle, Teradata and Greenplum, or that want to trim their staffing and equipment budget.

This goes to the heart of the AWS cloud proposition: take on a bit of risk in terms of availability, and in exchange get rid of expensive capital items and save on employee headcount, especially DBAs. A good thing for companies, certainly, but a somewhat frightening prospect for IT workers. ®

Similar topics


Other stories you might like

  • Everything you wanted to know about modern network congestion control but were perhaps too afraid to ask

    In which a little unfairness can be quite beneficial

    Systems Approach It’s hard not to be amazed by the amount of active research on congestion control over the past 30-plus years. From theory to practice, and with more than its fair share of flame wars, the question of how to manage congestion in the network is a technical challenge that resists an optimal solution while offering countless options for incremental improvement.

    This seems like a good time to take stock of where we are, and ask ourselves what might happen next.

    Congestion control is fundamentally an issue of resource allocation — trying to meet the competing demands that applications have for resources (in a network, these are primarily link bandwidth and router buffers), which ultimately reduces to deciding when to say no and to whom. The best framing of the problem I know traces back to a paper [PDF] by Frank Kelly in 1997, when he characterized congestion control as “a distributed algorithm to share network resources among competing sources, where the goal is to choose source rate so as to maximize aggregate source utility subject to capacity constraints.”

    Continue reading
  • How business makes streaming faster and cheaper with CDN and HESP support

    Ensure a high video streaming transmission rate

    Paid Post Here is everything about how the HESP integration helps CDN and the streaming platform by G-Core Labs ensure a high video streaming transmission rate for e-sports and gaming, efficient scalability for e-learning and telemedicine and high quality and minimum latencies for online streams, media and TV broadcasters.

    HESP (High Efficiency Stream Protocol) is a brand new adaptive video streaming protocol. It allows delivery of content with latencies of up to 2 seconds without compromising video quality and broadcasting stability. Unlike comparable solutions, this protocol requires less bandwidth for streaming, which allows businesses to save a lot of money on delivery of content to a large audience.

    Since HESP is based on HTTP, it is suitable for video transmission over CDNs. G-Core Labs was among the world’s first companies to have embedded this protocol in its CDN. With 120 points of presence across 5 continents and over 6,000 peer-to-peer partners, this allows a service provider to deliver videos to millions of viewers, to any devices, anywhere in the world without compromising even 8K video quality. And all this comes at a minimum streaming cost.

    Continue reading
  • Cisco deprecates Microsoft management integrations for UCS servers

    Working on Azure integration – but not there yet

    Cisco has deprecated support for some third-party management integrations for its UCS servers, and emerged unable to play nice with Microsoft's most recent offerings.

    Late last week the server contender slipped out an end-of-life notice [PDF] for integrations with Microsoft System Center's Configuration Manager, Operations Manager, and Virtual Machine Manager. Support for plugins to VMware vCenter Orchestrator and vRealize Orchestrator have also been taken out behind an empty rack with a shotgun.

    The Register inquired about the deprecations, and has good news and bad news.

    Continue reading

Biting the hand that feeds IT © 1998–2021