Cover photo
Nitin Borwankar
Works at Numericc Applications Inc
Attended IIT Bombay
Lives in sf bay area, usa
5,302 followers|198,681 views


Nitin Borwankar

Shared publicly  - 
Add a comment...

Nitin Borwankar

Shared publicly  - 
thought this was pretty funny - a meerkat getting drowsy and falling asleep
Mary Figliulo's profile photo
He must be at the same musical I was at.....
Add a comment...

Nitin Borwankar

Shared publicly  - 
An interesting conversation has been evolving on Twitter about the antifragility of server systems, DevOps etc.
The link below is one thread but there are a number of other threads so please dont take the one below as the only one.

 It was getting too long for Twitter, so I'm expanding on some thoughts here.

The desirable situation is similar to what happens in a human body, where weaker cells or bad cells die off leaving stronger ones.  This is an antifragile system where stressors make a system stronger.

The discussion is about analogies in the server and DevOps space.
Current  server systems are robust but not antifragile. Robust systems resist external force to a point but then collapse completely.

Antifragile systems adaptively get better with each external stressor.
The problem with applying this to server systems is twofold

a) There is no underlying statistical  model or underlying set of properties which admit of a statistical distribution where some part of the population may be considered "good" and the others "bad".  In fact in a server farm (whether in the cloud or not) all servers are started up with identical properties, intentionally.

It is therefore, IMHO, no way to assign a "goodness"  measure to a server and cause it to be "killed" off to improve the health of the larger  population of servers.

b) servers themselves do not adapt in the presence of external stress, in a way that changes their responses in future.  This is not how they are currently designed.  They are much more like bricks than human cells.

IMHO, there needs to be a layer in addition to existing server architecture that uses machine learning to do two things. But before I go there I want to say that the goal of this is not "finding bugs" as Netflix's ChaosMonkey does.

 It is to adaptively change parameters of the system so that with each stressor it becomes more resilient to future stressors. 

The problem IMHO is that we don't think of server populations as set of  properties that are random variables in the stochastic process sense, we think of each server as an identical copy of the other.  And a server is either up or down.  In our mental model there is no smooth transition where the server gracefully degrades, learns from the stress and the next time degrades less.  We want this second model where we think in terms of graceful degradation (smooth metric) rather than up/down (discrete metric)

The question is then threefold

a) What knowledge (attributes) do we want to extract, from the current  stressor, and from the current response, which might be useful in creating an adaptive loop.

b) what parameters in the server do we adjust after a stressor event, so as to degrade less in future.

c) how do we assign degrees of goodness(continuous metric) so that we can use certain servers preferentially over others .

Nicholas, Adrian,  et al - hope this makes sense.  Hard to do this on Twitter.


I am not sure the "killing off bad cells" analogy holds in a cloud but may hold in a non virtualized hardware server farm where some servers may have worse hardware.  The virtualization in a cloud, IMHO, spreads "badness" in ways that might make the above discussion inapplicable due to the non-localizability of "badness" to a particular server even if said server is made to look more like a cell not a brick.
Instantly connect to what's most important to you. Follow your friends, experts, favorite celebrities, and breaking news.
Add a comment...

Nitin Borwankar

Shared publicly  - 
Leo, our 6 month old German Shepherd
Pocyahstu Santana's profile photoSilvana Hammoud's profile photoTina Schraier's profile photomuhammad zaid's profile photo
Sammy dog beautiful
Add a comment...

Nitin Borwankar

Shared publicly  - 
Those who think they're unlucky should change their outlook and discover how to generate good fortune, says Richard Wiseman
Trevor Watson's profile photo
reckon it's pretty spot on
Add a comment...

Nitin Borwankar

Shared publicly  - 
The apes can draft a plan and communicate it with their troop
Add a comment...

Nitin Borwankar

Shared publicly  - 
Every nontechie and techie shou ld read this real evolving story of an accounting company with a backup nightmare.
Add a comment...

Nitin Borwankar

Shared publicly  - 
Part of +Neal Ford 's new functional programming video series for O'Reilly 
Add a comment...

Nitin Borwankar

Shared publicly  - 
Cricket is a lot easier to understand than Baseball
As the game Cricket becomes more visible on the global stage I've seen more articles by American authors who tried to get the hang of it and got all mentally tangled up in the really fringe details. So right here right now I'm going to explain the core similarities and core differences between Cricket and Baseball. Before I begin it's important to know that there are 3 major forms of Cricket and the one I'm going to talk about is the T20 or the Twenty 20 format. Once that is understood the others become easier to understand.

Core Similarities

* There are two teams with batters, pitchers/bowlers and fielders.
* Batters try to hit a ball thrown at them by a pitcher/bowler
* Fielders try to catch the ball in the air or stop its progress.
* When the ball is in flight, batters try to score by running between markers.
* At the end of the game the team with the most runs wins.
* A batter is "out" when they hit a ball in the air and it is caught by a fielder
* There is a "special" fielder who is positioned right behind the batter called a "catcher" in Baseball and a "wicketkeeper" in Cricket
* A batter is out when they run and don't complete the run before a fielder throws the ball back to a marker before they get there ("marker" = Base in Baseball, Stumps in Cricket)
* When a ball is hit all the way to the edge of the field without hitting the ground the it counts for multiple runs (anywhere between 1 and 4 in Baseball, 6 in Cricket)

Core Differences

* Cricket is played on the strip of ground called "the pitch", with a batsman/batter at each end. Baseball is played around a diamond shaped playing area with bases at the corners.
* In Cricket batters bat in pairs and run between the two ends of the pitch. When they safely exchange positions it's scored as a run. In Baseball a player runs around the diamond and when all foir bases are traversed it's a run.
* In Cricket the each end is are marked with three wooden sticks called stumps or wickets. Forcing an out is often referred to as "taking a wicket". In baseball there is a single home plate.
* In Cricket the strike zone is explicit and consists of the wickets, in Baseball the strike zone is implicit and left to umpire interpretation.
* In Baseball an innings is three outs and there are at least 9 and possibly more innings in a game
* In T20 Cricket an innings is 11 outs - the whole team bats, then the opposite team bats.
* In Baseball a pitcher can continue to pitch through the whole innings, in Cricket bowlers get a limited number of pitches.
* In Cricket bowlers bowl 6 piches at a time, then switch bowlers. The next bowler bowls from the opposite end of "the pitch".
* In Baseball the ball is pitched full toss always, in Cricket almost always the ball is bounced off the ground and this is used to gain advantage via bounce, spin and swing of the ball. While the ball can be pitched full toss in Cricket, almost always this is less attacking than a ball bounced off the ground.
Add a comment...
Data/math/science geek
Fan of the TV show Bones.  Also any somewhat wacky or eccentric show or person.  But it/they must be intelligent - else it's just weirdness.
Bragging rights
3 digit Twitter ID
  • IIT Bombay
  • University of Southern California
    Appl Math, Pure Math
  • Bombay Scottish HS
    High School
Basic Information
Other names
Contributor to
software developer, manager
  • Numericc Applications Inc
    Founder, 2014 - present
  • tagschema
    software developer, manager, 2012
  • ingres, sybase, ironport, couchone
Map of the places this user has livedMap of the places this user has livedMap of the places this user has lived
sf bay area, usa
mumbai, india - bangalore, india; los angeles ca usa
Contact Information