Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Oct 01, 2010
Google wants to shrink images transferred over the Internet by proposing a new lossy format called WebP. They claim they have achieved 39% reduction in image byte size leading to speedier page load.
WebP (pronounced "weppy" /(wĕpˈē)/) is an image lossy compression format developed by Google and meant to shrink the size of image files. Google claims that images and photos represent around 65% of the total bytes sent over the Internet these days, which is quite a significant share of all traffic. It is understandable that lowering the number of bytes per picture will have an impact on the average page size, speeding up page loads.
WebP uses a compression algorithm borrowed from the VP8 codec used by Google in WebM, the open source media file format for encoding and compressing video. The overall effect of using WebP is an average of 39% reduction in image byte size after converting 1,000,000 randomly chosen pictures, mostly JPEGs and some PNG and GIFs. Google affirms the image quality has not significantly degraded after the conversion.
WebP is meant to replace JPEG as a better lossy compression format. WebP images are delivered into a lightweight RIFF container, adding a small number of bytes per picture (minimum 20 bytes) but having the ability to contain more in case the picture should be accompanied by more meta-data.
Currently Google is providing a free open source decoder and a conversion tool for Linux x86 64-bit. A Windows version is due in the near future. Google is also working on a WebKit patch enabling Chrome to display WebP images.
An image gallery has been set up to allow anyone to compare the quality of WebP images against their JPEG originals. WebP images have been encapsulated into a PNG container so they can be seen with actual browsers.
Google plans to add support for a transparency layer in the future. WebP belongs to Google’s initiative "Let's make the web faster" including projects like Page Speed, Speed Tracer, and SPDY.
RDBMS to NoSQL: Managing the Transition
Why NoSQL? A Primer on the Rise of NoSQL
Adopting Git for the Enterprise: Risks and Considerations
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
Reducing the data sent by 25% can mean a lot of savings for everyone. Not just people paying for bandwidth/hosting. For those with metered internet accounts, reducing file size lowers your monthly usage.
Alternative take on webP:
x264dev.multimedia.cx/?p=541
Whatever the technical arguments: a 39% improvement doesn't sound like much of an argument for introducing a whole new image format.
Now, whatever the quality of Google's new format (I haven't even looked at any example images yet) I am absolutely boggled that anyone could say a potential 40% performance improvement wasn't worth at least trying.
It would be good if the article had a section about the patent issues.
Most HTML in web pages is bloated with tons of noisy HTML due to the lack of CSS knowledge. Going a step further, most applications don't pay attention to acceptance of compressed pages.
Richard L. Burton III
Co-Founder of SmartCode LLC
www.SmartCodeLLC.com
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
5 comments
Watch Thread Reply