Search

Kei Kubo Phones & Addresses

  • Belmont, CA
  • San Francisco, CA
  • San Jose, CA
  • Northfield, MN

Resumes

Resumes

Kei Kubo Photo 1

Chief Executive Officer

View page
Location:
935 Old County Rd, Belmont, CA 94002
Industry:
Internet
Work:
fluxflex, inc. since Jun 2010
CEO

Nagasaki!Nagasaki! since Sep 2006
Founder

Hatena Co., Ltd. Aug 2008 - Aug 2008
Internship

CSSEZ Jul 2007 - Aug 2008
Founder
Education:
Carleton College 2005 - 2010
B.A., Computer Science, Political Science
Skills:
Cloud Computing
Javascript
Interests:
Auto Scaling
Aws
Cloud Computing
Network
Infrastructure
Kei Kubo Photo 2

Ceo At Fluxflex, Inc.

View page
Position:
CEO at fluxflex, inc., Founder at Nagasaki!Nagasaki!
Location:
San Francisco Bay Area
Industry:
Internet
Work:
fluxflex, inc. since Jun 2010
CEO

Nagasaki!Nagasaki! since Sep 2006
Founder

Hatena Co., Ltd. Aug 2008 - Aug 2008
Internship

CSSEZ Jul 2007 - Aug 2008
Founder
Education:
Carleton College 2005 - 2010
B.A., Computer Science, Political Science
Skills:
Cloud Computing
JavaScript
Interests:
cloud computing, AWS, auto scaling, infrastructure, network
Honor & Awards:
IPA Exploratory IT Human Resources Project Award, 2008

Business Records

Name / Title
Company / Classification
Phones & Addresses
Kei Kubo
President
FLUXFLEX, INC
Custom Computer Programing · Nonclassifiable Establishments · Telephone Communications
169 11 St, San Francisco, CA 94103
601 Montgomery St, San Francisco, CA 94111
Kei Kubo
Director, President, Secretary, Treasurer
West Japan Bus Lines
300 N College St, Waterford, MN 55057

Publications

Us Patents

Shared Scaling Server System

View page
US Patent:
20120233313, Sep 13, 2012
Filed:
Mar 11, 2011
Appl. No.:
13/045586
Inventors:
Hironobu Fukami - Tokyo, JP
Kei Kubo - San Jose CA, US
International Classification:
G06F 15/173
US Classification:
709224
Abstract:
The shared scaling server system of the present invention comprises a plurality of client terminals for transmitting a request, an application load balancer for distributing the request transmitted by the plurality of client terminals, a plurality of application servers for processing the request distributed by the application load balancer, a main server connected to the application load balancer and the plurality of application servers and having a monitor and a controller. The monitor monitors load status of the plurality of application servers, the monitor detects a site, in which access to a resource of at least one application server is increased when the monitor judges that load status of the at least one application server exceeds a threshold, the monitor checks availability of a resource of the plurality of application servers, the monitor transmits information about the availability of the resource of the plurality of application servers to the controller. The controller, depending on the information, processes traffic of the site, in which access is increased, in an available resource of the plurality of application servers and the controller, depending on the information, activates a new application server when there is no available resource in the plurality of application servers, allocates a firm comprising the site, in which access is increased, to an available resource of the new application server and processes traffic of the site, in which access is increased, in an available resource of the new application server.

File Synchronization Method

View page
US Patent:
20120233116, Sep 13, 2012
Filed:
Mar 10, 2011
Appl. No.:
13/044641
Inventors:
Hironobu FUKAMI - Tokyo, JP
Kei Kubo - San Jose CA, US
International Classification:
G06F 17/30
US Classification:
707620, 707E17005, 707E17032
Abstract:
The present invention is a method of synchronizing files on a system including a client terminal, a management server, a test server and a production server, the method comprising the steps of: detecting, by an application installed on the client terminal, update of a file in a directory which the application manages; creating, by the application, an update history and difference information of the updated file; transmitting, by the application, the update history and the difference information to the management server; updating, by the management server, a file based on the update history and the difference information; transmitting, by the management server, the update history and the difference information to the test server; updating, by the test server, a file based on the update history and the difference information; displaying, by the test server, information of the updated file when a request to access the test server is transmitted by the client terminal; detecting, by the application, a request of deployment; transmitting, by the application, the request to the management server; detecting, by the management server, difference information between file management information of the test server and file management information of the production server; transmitting, by the management server, the detected difference information to the production server; updating, by the production server, a file based on the difference information; and displaying, by the production server, information of the updated file when a request to access the production server is transmitted by the client terminal;whereby the file of the production server is synchronized with the file of the client terminal.
Kei Kubo from Belmont, CA Get Report