melva.®
EMMANUEL SILVA / SOFTWARE ENGINEER
THE CORE / ENGINEERING, REVEALED.

Engineering
what comes
next.↗

Backend systems. Thoughtful architecture.
Reliable software, from the inside out.

Explore my workGet in touch
Interlocking metallic system core
SYS.CORE / 001
STRUCTURE → CONNECTION → POSSIBILITY
01API02Authentication03Services04Database05Integrations06Infrastructure
+FORM FOLLOWS FUNCTION.
EVERY LAYER HAS A PURPOSE.
↓ SCROLL TO EXPLOREMELVA® / ENGINEERING IN MOTION
01THE WAY I THINK

Complexity, engineered
into clarity.

I design and build software where architecture, reliability, and business needs come together.

A little more about me
01

Backend engineering

02

Software architecture

03

Database & integrations

04

Quality & reliability

02SELECTED WORK

From the problem.
Through the system.

Explore the thinking behind the interface.
Two academic projects. Distinct engineering foundations.

All projects
01 / 02Education platformSYSTEM STUDY / CLASSUP
CLASSUP / SYSTEM EXPLORER01 — 03
TUTORS / STUDENTS / GUARDIANS

Three roles. Shared context.

Tutors, students and guardians use the platform to manage academic progress and communication. The model illustrates their shared entry point into the learning journey.

CONCEPTUAL SYSTEM MAP · SELECT A LAYER TO EXPLORE

ClassUp

One learning journey. Three perspectives.

Bringing tutors, students, and guardians together around academic progress and communication.

Oracle Autonomous DBAWS LambdaGit Flow
01

A relational data foundation

Oracle Autonomous Database is the project’s relational store. Academic progress connects people and activities; relational modeling offers an explicit way to express those relationships.

02

Cloud function execution

AWS Lambda provides the project’s cloud execution foundation. A function boundary makes the distinction between the web experience and server-side execution visible.

03

A structured collaboration workflow

Git Flow is part of the project’s version-control approach. It gives collaborative development a shared branching vocabulary and separates ongoing feature work from integration.

Explore ClassUp
02 / 02Academic managementSYSTEM STUDY / UNICLASS
UNICLASS / SYSTEM EXPLORER01 — 03
ACTIVITIES / STUDENTS

The university workflow.

The project focuses on academic activity management and student tracking. This conceptual entry layer represents how those university processes meet the application.

CONCEPTUAL SYSTEM MAP · SELECT A LAYER TO EXPLORE

UniClass

Academic activity. A coherent system.

An academic activity management system designed around university processes and student tracking.

C#.NET CoreDesign patternsCloud architecture
01

A C# application foundation

UniClass uses C# and .NET Core. This gives the academic management application a typed foundation for expressing behavior and organizing the system around its domain.

02

Structure through design patterns

Design patterns are part of the project’s stated engineering approach. Their role is to organize recurring application responsibilities around academic activities and student workflows.

03

A cloud architecture perspective

Cloud architecture is part of UniClass’s technical foundation. It places deployment and execution concerns alongside application structure in the overall system design.

Explore UniClass
ALSO IN PRACTICE

Enterprise ERP development, database optimization and payment integrations.

Professional experience
03BEHIND THE ARCHITECTURE

Good systems.
Thought through.

Every connection is a decision.
Explore the layers behind reliable software.

INTERACTIVE SYSTEM STUDY01 — 08
03 / CONTRACT

API layer

A clear boundary between applications and business behavior. Validate requests, return consistent responses and keep integration contracts explicit.

ASP.NET Core · REST · Node.js
SELECT A LAYER TO EXPLORE↖

CONCEPTUAL ARCHITECTURE · An illustrative system, independent of any specific project.

04ENGINEERING CAPABILITIES

The right tools.
A deeper understanding.

From data models to deployment.
A foundation built through hands-on work.

01

Backend & APIs

Clear contracts. Dependable systems.

C#ASP.NET CoreNode.jsTypeScriptREST APIsExpress.js
02

Data engineering

Structure at the heart of every solution.

OracleSQL ServerPL/SQLEntity FrameworkADO.NETTypeORM
03

Architecture & integrations

Connecting the pieces that matter.

Software architectureDomain modelingAuthentication & authorizationEnterprise integrationsMVCOOP
04

Quality & infrastructure

Built with the next release in mind.

xUnitMoqAutomated testingDockerAWS LambdaAzure FunctionsAzure DevOpsCI/CDGitPostman
05PROFESSIONAL EXPERIENCE

Grounded in practice.
Always moving forward.

Enterprise software and databases.
Experience across the system lifecycle.

2025 — NOW
BRdata Tecnologia LTDA

Mid-Level Software Developer

May 2025 — Present

  • C# applications across .NET Framework, .NET Core and WinForms, covering the ERP development lifecycle.
  • ASP.NET API integrations hosted on AWS Lambda and Azure Functions.
2024 — 2025
Aliare

Oracle Database Administrator

Mar 2024 — Apr 2025

  • Oracle query optimization and routine database maintenance.
  • RMAN configuration, Flashback Queries, EXPDP backups and tablespace maintenance.
2023 — 2024
BRdata Tecnologia LTDA

Junior Developer

Apr 2023 — Feb 2024

  • C# applications and MVC projects with SQL database integration.
  • REST APIs and payment integrations with PicPay, PagBank and Itaú.
06OFF THE CRITICAL PATH

Serious engineering.
Room to play.

Where structure meets curiosity.
Experiments from this portfolio.

EXPERIMENT 001 / MELVA 2.0

Structure in motion.

A study in connected systems, metallic geometry and interactive architecture. Built as part of this portfolio.

Enter the lab
WEBGL / INTERACTIONEXPERIMENT 002

When the service fails.

Step through bounded retries and exponential backoff.

503 / 503 / 200
LET’S START A CONVERSATIONTHE NEXT CHAPTER / TOGETHER

Let’s build something
exceptional.↗

LinkedIn GitHub Résumé