CQRS, Event Sourcing, Rust, Typescript, Alloydb

Stuff I do: CQRS, Event Sourcing, Distributed Systems, Blockchain, Crypto, DeFi, and ERP integrationsTech Stack: Rust, Node, TS, Apollo, GraphQL, GCP, Firestore, Jest, Infura, Geth, Parity, Web3, Inversify, Tsoa, Gitlab CIIntegrated parity trace module to internal workflow to enhance txn meta data of pre-Byzantium fork txn.Created integration with QBO and Netsuite that allows linking of vendor/customer invoices to txn that handles exchange rate differences.Built a data sync service to fireblocks using GCP workflow engine to continuously pull custodial txn and vault balances to main API. Generalized Netsuite custom field integrations to allow pushing blockchain data to Netsuite transactions to allow customers to aggregate data within Netsuite.Created and maintained internal pricing engine that does multi step valuation of digital assets from multiple sources while allows for different valuation methods. Enhanced to handle time zone to allow daily valuation using the same time zone as the customer.Multi currency and crypto base invoice and bill payment valuation and integration. If you know what this means, then we can be friends.CQRS event sourcing system, built the blockchain model state machine.

bpftrace, perf_event, bcc, aya-rs, nodePrototyped no code low overhead monitoring agent using bpftrace to capture request and response, and capture stack trace of node application for future comparison. Currently working on nodesnoop using bpftrace to monitor node internals and profile event loop performance.

Typescript, GraphQL, Prisma2, Heroku, React, Apollo, Nexus, Postgres, ESLint Plugin, Auth0, Stripe, Docker, Cypress, Segment, HubspotHeroku CI executes Cypress... probably the second hardest thing I had to do. Used Bash to create runtime env as static asset for React app, avoided unnecessary rebuild during staging to prod promotion, leveraged Heroku dyno auto restart ability to generate the run time envCreated a linter repo to standardize code formatting and ESLint rules for the entire organization. Built a custom ESLint plugin around AlexJS as an inclusivity initiative. Went down the rabbit hole of AST and visitor pattern with no regret.Worked on review app seeding and ticket system integration to allow stakeholders to access deployed review apps directly in the ticket system.Decoupled Nexus Experiment to Nexus/Prisma/Apollo and managed the backward incompatibility of Prisma cli.Auth pipeline and guards using Auth0.Permission layer using graphql-shield. Built segment integration with action/dispatcher pattern, leveraged TS type hinting to show parameters of actions.

React, Redux, NestJS, Typescript, AWS through Terraform, Python, Express, PostgreSQL, WebSocket, GitHub Actions (Bash), Jest, SSE, D3, Tesseract, Docker, Supertest, Wordpress, PHP. 1st favorite thing that I built is the automatic creation of environments based on PR to improve QA workflow based on different labels on the PR.2nd favorite thing that I built is the integration of sensors and our member portal through SSE that comes with JWTS authentication. Front end was built with Mapbox GL to optimize performance of map loading. This was truly exciting and I still don't quite know how the Sr Dev embedded all those coordinates but it was a really fun project.3rd favorite thing was a half blown CI/CD pipeline that kicks off cypress. I was able to use mocha reporting tools to compile a report of the run.4th favorite thing is automating front end blue green deployment. This task actually allowed me to find ways how AWS doesn't work the way I think it does. The final solution included Lambda@Edge and using custom headers. 5th favorite thing is fuzzy live search for locations and markets on our WP public website.Honorable Mentions:A bunch of custom Github actions. Really wish I could share them with the world because they're amazing. (like appending URL of your ad hoc env to your PR, or uploading your source maps to Sentry, who doesn't want that?) A centralized messaging module service with a throttling patch ontop of SQS. Built with abstract class to define service provider interface that allows us to swap out service providers with ease. A shared module in the API to upload images and resizes with Lambda, then save the path in the DB. Only reason it's honorable mention and not my favorite thing is because I built it with a subpar solution. My implementation made the upload tie to the payload size of the Lambda. I'm still waiting for my chance to refactor the module.Custom WP plugin registry through satis hosted on s3 static website.

JSparring | Javascript Algorithm PVP Challenge Web AppLeveraged React to build an interactive user interface which limited duplicating codes by creating reusable components that allowed application to seamlessly render multiple dynamic components with minimal impact on user experienceBuilt a Websocket server using Node to establish duplex streams of communication with client, relied on the protocol’s unique ability to receive and transmit data with minimal overhead to deliver information real-time from server to clientKubricks | Kubernetes Port MapperUtilized Docker to containerize a fullstack React application to leverage Docker’s integration with Kubernetes container runtime interface which streamlined deployment of resources over a variety of hosting environmentsDeveloped Kubernetes deployment YAML files to allow development team members to deploy clusters with similar cluster composition locally on Minikube in order to jump start development of a Kubernetes visualization toolImplemented a SQL database to support testing cluster using AWS RDS during initial developmental phase to take advantage of the accessibility and consistency of AWS which allowed team-wide access to the same databaseOptimized Kubernetes API Server queries to decrease Express server overhead and latency by modularizing API requests based on cluster resource types and using field-selectors to filter requests at the API serverCreated a SQL database for user registration microservice as a cluster resource hosted by GCE to decrease the number of reads and writes to one single database by using Postgres Docker image configured for Persistent Volume