Alexey Bokov's weblog » work

Windows Azure CDN

Alexey Bokov — Tue, 21 Feb 2012 08:10:19 +0000

Windows Azure CDN locations : 24 locations for February 2012 – also see list of Windows Azure CDN node locations
Windows Azure CDN Helpers : simple library of MVC helper methods that will allow you to quickly integrate the Windows Azure CDN into your web application to speed up your site
Using the Windows Azure CDN for Your Web Application
Working with the ASP.NET OutputCache module for CDN Friendly HTTP Headers, vary:* Headers, compressed content with the CDN, use of IIS Virtual Application, provide your own OutputCache module implementation – Hosted Service as a Windows Azure CDN Origin Tips . Great post by Shawn Cicoria.
Serving GZip compressed Content from the Azure CDN
Windows Azure Content Delivery Network – Hands-On Lab

Smartphone patent war

Alexey Bokov — Mon, 22 Aug 2011 13:34:11 +0000

update : Also take a look on Forbes analitycs : Identifying The Tech Leaders In LTE Wireless Patents

Job interview via facebook – they’ll ask abt ur skillz and propr kmand of ze English lng

Alexey Bokov — Fri, 22 Jul 2011 05:38:32 +0000

“They’ll ask abt ur skillz and propr kmand of ze English lng”

Cloud computing humor

Alexey Bokov — Wed, 13 Jul 2011 12:43:56 +0000

Smartphone platforms market share – July 2011

Alexey Bokov — Wed, 13 Jul 2011 07:25:13 +0000

MySQL create user and add table

Alexey Bokov — Mon, 11 Jul 2011 12:05:07 +0000

Short how-to:
root@215003:~# mysql -u root -p Enter password: mysql> CREATE DATABASE s_db; mysql> GRANT ALL PRIVILEGES ON s_db.* to 's_user'@'localhost' IDENTIFIED BY '12345678'; mysql> FLUSH PRIVILEGES; mysql>exit mysql -u s_user -p s_db < database.sql <code>

Hello World!

Alexey Bokov — Fri, 10 Jun 2011 12:42:05 +0000

Which mobile platform will be most important in 2011?

Alexey Bokov — Thu, 13 Jan 2011 16:55:24 +0000

Interesting poll in linkedin – results ( as expected ) – Android is first :

Links for January 2011

Alexey Bokov — Sat, 08 Jan 2011 15:19:52 +0000

AWS Case Study: U.S. Department of State – ExchangesConnect Video Contest
RESTful Services with Erlang and Yaws : wting RESTful web services in Erlang/YAWS
Amazon moves VMware’s virtual machines to the cloud, blog post on AWS :VM Import – Bring Your VMware Images to The Cloud
Android vs iPhone: Security Models
Hudson Project Renames to Jenkins – also see Hudson’s future on hudson-labs.org, On Oracle proposal about Hudson by Kohsuke Kawaguchi
Skype architecture
Real customers feedback on Agile
Amazon’s Android Appstore : Amazon launches Android appstore portal, Amazon’s Disruptive Android App Store Now Open To Developers — Full Details, Deciphering Amazon’s Android App Store Strategy
The coolest open source databases on the planet (NOSQL + RDBMS)
NoSQL at twitter
The experiment infrastructure at Google
Chrome Release Cycle
Google presented Android 3.0 ( Honeycomb ) on LG /G-Slate device: What’s Hiding Inside Android’s Honeycomb?, and LG and T-Mobile’s G-Slate Tablet To Run Android 3.0 Honeycomb, demo videos from CES :CES 2011: T-Mobile G-Slate Honeycomb LG Tablet Hands-on Videos – Features Walkthrough in 8 New Videos
Korea : Telecoms bet on cloud computing – SK telecom announced cloud data center for mid- and small-business, other players – KT Corp. and LG Uplus also announced their plans last year to jump into competition.
CloudBees announced HaaS : Hudson as a Service ( free accounts still available )
Sony announced ( actually in Nov/2010 ) Sony’s next-gen app platform will use Objective-C/GNUstep: SNAP. By the way Sony got some open source stuff : Sony products with Linux / OSS embedded Technology.

Below I put some snapshots from Googl’e chrome release cycle presentation with some comments.

They originally planned this :

And got a lot of troubles with this cycle like :

Long lived branches, which : Made supporting the branch (i.e. merging changes) more difficult as we drifted further from the trunk…
Unpredictable release cycles, with date targets we could never hit, and….
Engineers who were always in a rush to get their features into “this” release since we couldn’t make any promises about the schedule
so they slightly change ( and simplify ) it to this 3 channel diagrams by making release shorter ( and reduce scope )

So they change traditional scheme to this one :

And then make it work in real life by cutting scope at release ( by disable features ) : Establish clear expectations (and engineering practice) to developers that any features not ready to ship at branch will be disabled (i.e. we only cut post branch, never add).

So it works fine for google guys and their rules are :

The branch point is the end of our development cycle
Features only get disabled post branch point
Features should be engineered so that they can be disabled easily (1 patch)
Only stability, security, and critical regressions can ever block a release

For me it’s looks fine for in-house development, but for me it’s big question how to apply same scheme for outsource development.

Lucene – all about distributed and real time search

Alexey Bokov — Sat, 08 Jan 2011 15:13:31 +0000