Daniel Fridkin · Home
Back to projects

Backend Engineering / Automation

Backend and Internal Automation Tools

Builds backend services and automation tools that connect infrastructure workflows with application needs.

Ongoing

Component overview

Connect operational workflows to services

A conceptual overview of the backend and automation building blocks used across internal tooling, rather than one specific deployed service.

  1. Model the workflow

    Turn repeated operational tasks into service logic.

    • Go
    • Node.js
    • Python
    • PHP/Laravel
  2. Expose useful interfaces

    APIs and service-oriented integration patterns.

    • REST APIs
    • WebSockets
  3. Connect data services

    Database-backed workflows and supporting data systems.

    • MySQL
    • MongoDB
    • Redis
    • Elasticsearch

The challenge

Infrastructure teams often need purpose-built tools that turn operational workflows into reliable APIs, services, and automations.

The approach

Built backend and internal tooling with Go, Node.js, Python, PHP/Laravel, databases, REST APIs, WebSockets, and automation-first design.

My role

Combined backend implementation with DevOps context to create practical tools that are useful for developers and operations.

Engineering decisions

Automate recurring operations

Build purpose-specific tools where repeated manual work can become a reliable workflow.

Keep operational ownership in the design

Combine backend implementation with the infrastructure context in which the services will operate.

Scope & delivery

  • REST APIs, WebSockets, and service-oriented backend patterns.
  • Automation tools that reduce repeated manual work.
  • Database-backed workflows with MySQL, MongoDB, Redis, and Elasticsearch.
  • Backend systems designed with operational ownership in mind.
Next projectAbuse Detector