Maxim Fedchyshyn

San Francisco, CA, United States

Member since July 6, 2016

Over the years, Maxim has managed the infrastructure of different levels, from a two-person startup to a multi thousand-strong corporation. Upon starting a new project, he pushes to adopt industry best practices while following the motto, "Move fast, think big." Both an individual contributor and a team player, he favors quality, failover, and reliability. He is passionate about containers and the infrastructure-as-a-code paradigm.

...thing I've built is a distributed backup system for a twenty-node sharded MongoDB cluster before a reliable official online backup solution existed.

Employment

Infrastructure Architect and Adviser

Motorola Solutions

2017 - PRESENT

Reviewed existing infrastructure and prepared recommendations to optimize cost efficiency without reducing functionality. After implementing it, the company managed to save over USD $150,000 for the first year on the pilot chunk of infrastructure.

Technologies: AWS Stack

Senior DevOps Engineer

Zillow.com

2016 - 2017

Migrated the whole infrastructure for one of Zillow departments from RightScale to Terraform+Packer, thus implementing the infrastructure-as-a-code paradigm.

Designed and implemented the core infrastructure that runs on up to 80 hardware CentOS servers and on-demand AWS resources with up to 500 instances.

Provided system administration for the database, which was over 7TB in size with total caching of 2TB+. MongoDB's team claimed that we were the biggest client for their online backup solution.

Developed the system to be fault-tolerant. During a major datacenter failure (40% of all servers offline), the website stayed online through incoming traffic topping 1000 Mbps. It has since scaled up to 40 million monthly visitors, with 25k connections/second during peak load.

Wrote 88k lines of Ansible's playbook, covering 37 server roles. Within a year, brought 21 developers to contribute to the repository.

Sharded MongoDB Backup Solution (Other amazing things)

Migrated to MongoDB and brought the system to a twenty-node sharded cluster, building the backup solution for the sharded environment on my own since Mongo did not provide one. Discovered several non-critical and a few critical bugs to be fixed in MongoDB's next release.