Skip to content

Latest commit

 

History

History
127 lines (97 loc) · 7.81 KB

resume.en.md

File metadata and controls

127 lines (97 loc) · 7.81 KB

Resume

Profile

Summary

  • Designed and developped a distributed Object Storage System at Yahoo! JAPAN using Go and Cassandra.
  • 5 years of experience in Golang programming.
  • Technical leadership experience (up to 6 members)
  • Experience in developing / managing a web service personally.
  • TOEIC score 780.

Technical skills

  • Language: Fluent in Go and working knowledge of C++, Java and PHP.
  • Database: Fluent in Cassandra and working knowledge of MySQL.
  • OS: Linux (Red Hat based)
  • Extremely creative with problem solving skills.

Work experience

Yahoo! JAPAN (2008 - )

  • Joined a project to develop a Object Storage as a jounior engineer. (2009-)
  • Joined a project to introduce NoSQL distributed database to the company. I had some performance surveys for some Open Source database software. After the introduction of Cassandra, I supported trouble shootings to solve problems happen in the operation. (2012-)
  • Designed and developped "Dragon" a new object storage as a tech lead of a small team (2014-).
    • After the launch in Jan 2016, continued to improve the product.
    • Dragon was storing over 11PB and 20Billion objects as at Nov 2017.

Merpay (2019 - 2020)

Freelance( 2021 - )

  • Started working as an freelance engineer since 2021.

Publications

Go

Cassandra

  • slide: Cassandra Summit 2016 注目セッション報告 (in Japanese) (2016/10/12)
    • A participation report of Cassandra Summit 2016 at "Cassandra meetup in Tokyo, Fall 2016". I summarized and introduced a presentation on the improvements of storage engine in Cassandra 3.0.

Dragon

Open Source Software contributions

Go

Cassandra

  • Improved SELECT latency for large partitions by 40% (2016/10/04)
    • Ticket: [CASSANDRA-12731]
    • Merged in Cassandra 3.10.
    • Just small amount of code, but the removal of in-memory cache gained efficiency.
    • Also fixed a bug in compaction process which I found in the work.
  • Add Prepared CQL statement to query trace records to improve traceability of query execution performance. (2016/05/06)
  • Investigated and reported a serious data-collapsing bug produced during upgrading to Cassandra 3.0. (3/17/2017)
    • Our team members including me patiently found a way to reproduce the issue which was accidentally found in our cluster.
    • The issue was fixed in priority "Urgent" by the Cassandra committers.
    • Ticket: CASSANDRA-13125, CASSANDRA-13320

others

Personal technical output