Hide Contact

Phillip Adler

pcadler@gmail.com

818-518-4354

Github

Github

Resume

Picture of the author

About Me

I am an Aspiring Software Developer and Developer Operations Engineer whos interests span Backend Development, Database Management, DevOps, and System Administration. I have broad experience using relevant technologies and tools in a home Lab environment. I also, albeit being less focued on it, have experience in Frontend Development, and have used Flutter in the past to build a mobile frontend, and React recently to build web applications.

Skills

DevOps

Docker

Kubernetes

OpenEBS

Helm

Terraform

Ansible

Jenkins

Gitlab

Github

Git

CI/CD

Prometheus

Grafana

Keycloak

AWS

Packer

Backend Development

Nodejs

Express

Go

Python

.NET

Spring Boot

C#

ASP.NET

REST

gRPC

SQL

MongoDB

PostgreSQL

Cassandra

Redis

Kafka

RabbitMQ

Systems Administration

Linux

FreeIPA

LDAP

Kerberos

Samba

NFS

SAMBA

GRUB

KVM

QEMU

VirtualBox

Vagrant

Networking

Frontend Development

React

Redux

TailwindCSS

Flutter

Dart

NextJS

HTML

CSS

Interests

I am interested in how objects are stored, represented, transmitted, and secured across networks, databases, and web applications. My favorite subject in school was Databases, where we learned about how Databases deal with Concurrency, Transactional Integrity, Index Data Structures For Queries For varying query manners, such as Geospatial, General, Full-Text Search, and Approximate Nearest Neighbor Searches. For Personal Projects I have used Databases for each of these purposes and have spent a lot of effort to understand best case use scenarios, tradeoffs, and general manners of how each type of database engine deals with certain queries.

I also found network interesting, and in particular learning about BGP was transformative to my idea of what truly makes a network and a networking device. I have also ventured into experimentations in VM / Container Setups to understand how different drivers deal with traffic routing. For example, how does the default Docker Bridge Engine route traffic to your containers? This would be based on the fact that Docker spins up a bridge network on your host machine, spins up a network namespace for each container, and then uses a veth peer to set up a connection between the bridge network and the containers network namespace, and adds routes to your host machine to the bridge. Then when you move to networking drivers that implement the CNI specification, and needs to manage routes accross multiple nodes, you deal with an extended problem set.