egabriel.dev · tty1 · simulated boot (illustrative)
  1. GE-BIOS v2.6 · egabriel.dev portfolio platform
  2. CPU0: backend/cloud engineer · distributed systems
  3. Memory test: 16384M ... OK
  4. Boot device: static output · booting kernel
  5. [ 0.000000] portfolio-kernel 1.0 (static output) #1 SMP
  6. [ 0.018342] edge: HTTPS terminated at hosting provider[OK ]
  7. [ 0.041207] edge: security headers loaded[OK ]
  8. [ 0.052911] lsm: content-security-policy enforced (self + hashes)[OK ]
  9. [ 0.077915] fs: mounted version-controlled content[OK ]
  10. [ 0.112906] runtime: interactive components registered, loaded on demand[OK ]
  11. [ 0.163380] net: public API mapped at /api[OK ]
  12. [ 0.187004] api: contract published at /api/openapi.json[OK ]
  13. [ 0.201377] storage: no block device found (no database, by design)[SKIP]
  14. [ 0.224551] mail: contact delivery provider not configured[WARN]
  15. [ OK ]Started systems.service
  16. [ OK ]Started principles.service
  17. [ OK ]Started about.service
  18. [ OK ]Started resume.service
  19. [ OK ]Started contact.service
  20. [ OK ]Reached target portfolio (rack wall online)
Welcome...
Skip to content
GE.
Menu

Backend / Cloud Software Engineer

Gabriel Emmanuel

I design and build backend systems that hold up in production.

Distributed Systems · APIs · Cloud

Inspect systems →Read résumé
Currently
Founder & Engineer, Scalefort
Also
Senior backend engineering — Norebase, First Bank
Focus
Reliability · API design · Cloud architecture
~/systems

Selected systems

Selected systems I've designed, built, or helped evolve.

All systems →
01● LIVE

Komuvo

Estate & Community Management Platform

Estate management, payments and security on one platform: resident records, visitor passes, guard patrols, maintenance requests and a shared wallet for bills.

ROLE
Architecture · Backend · Technical Direction
Inspect system →
02● LIVE

Datara

AI-Powered Business Intelligence

Turns everyday business data into decisions: explains what changed, why it changed and what to look at next, and answers plain-English questions without needing an analyst.

ROLE
Architecture · Backend
Visit system →
03● BETA

Foodbot

AI-Powered Nutrition App

Meal planning for Nigerians, with a focus on African cuisine: AI recipes, weekly plans, shopping lists, nutrition tracking and live nutritionist sessions.

ROLE
Backend · Application Architecture
Visit system →
04● IN DEVELOPMENT

SchoolOS

School Management Platform

Runs the whole school for Nigerian and West African schools: admissions, attendance, results, report cards, fees and parent communication, built for low bandwidth and mobile.

ROLE
Architecture · Backend
Not yet liveCase study coming
05● IN DEVELOPMENT

Ofiis

Virtual Office for Remote Teams

A virtual office for African remote teams: see who's free, focusing or in a meeting, and start a conversation in one click, even on a bad connection.

ROLE
Founder · Architecture
Launch planned for 2027Case study coming
~/failure-lab

What happens when things fail?

Systems fail. The interesting part is what happens next. This simulation shows how a well-built payment flow behaves when a dependency stops cooperating.

Simulated logs · payment-serviceidle

$ waiting for requests

Failure controls
  • TimeoutON
  • RetryON
  • Idempotency
  • Circuit breakerON

More safeguards become switchable in a later version.

Start with a healthy request.

~/principles

Complexity should be earned.

Every service, queue, cache, and abstraction should exist because a specific constraint requires it.

Read principles →
  1. 01Start simpleStart with the simplest architecture capable of solving the problem.
  2. 02Design for failureNetworks fail, APIs time out, messages arrive twice. Production software should expect it.
  3. 03Observability is a featureLogging, tracing and metrics are part of system design, not an afterthought.
  4. 04Data is architectureDatabase decisions are architecture decisions.
  5. 05Understand the trade-offThe goal is not maximum sophistication. The goal is the appropriate trade-off.
~/toolbox

Backend toolbox

Organized by responsibility.

Backend
  • Server-side development
  • REST APIs
  • API design
  • Payments
Data
  • Relational data
  • Analytical data
  • Caching
  • Data modelling
Cloud & Infrastructure
  • Cloud platforms
  • Containers
  • CI/CD
  • Serverless
Architecture
  • Distributed Systems
  • Event-Driven
  • Change Data Capture
  • Microservices
  • Background Processing
Frontend when required
  • Web applications
  • Dashboards
~/under-the-hood

Under the hood

You're currently using one of my projects.

Most pages on egabriel.dev are static content; a few interactive parts (the Failure Lab and API Explorer) talk to a small public API.
Static first

Pages render to static HTML. JavaScript only loads for the parts that need it: the Failure Lab and the API Explorer.

The database decision

There is no database because this portfolio doesn't need one.

Most portfolio content is version-controlled and changes infrequently. Adding a database would increase operational complexity without solving a real problem.

Open to consulting

Need a backend that holds up in production?

Architecture reviews, resilience hardening, payment flows, or backend development. Tell me about your constraints.

Discuss a project →contact@egabriel.dev