A. Akash Achary
Software Developer building reliable backend systems in Java and Spring Boot — from service architecture to the production concerns that keep them running: observability, testing, and failure handling.
A typical request through a service Akash builds
Hover or tab through a node to see what it does.
01 · About
Backend-first, full-stack when it matters
Akash is a backend-focused software developer with about three years of professional experience, currently building services at Signovate Technologies. His work centers on Java and Spring Boot: designing REST APIs, modeling data with JPA/Hibernate, and reasoning about the distributed-systems problems that show up once a service stops being a toy — message ordering, retries, caching, and observability. He also works comfortably across the stack when a project calls for it, including React/Node full-stack builds and applied computer-vision work.
Education
B.Tech in Information Technology
NIST University
Education
Diploma in Mechanical Engineering
Gandhi Polytechnic College
02 · Experience
Where the work has actually happened
AUG-2023 — Present
CurrentSoftware Developer
Signovate Technologies Pvt. Ltd.
Backend development on Java/Spring Boot services: REST API design, data persistence with JPA/Hibernate, microservice patterns, and the day-to-day production work of testing, debugging, and monitoring services after they ship.
- Designing and implementing REST APIs with Spring Boot
- Service-layer and repository-layer design with Spring Data JPA / Hibernate
- Working with relational databases (MySQL, Oracle) and query design
- Applying microservice patterns and inter-service communication
- Writing tests with JUnit and Mockito; BDD scenarios with Cucumber
- Instrumenting services for observability (logging, monitoring)
- Working with containerized environments (Docker) and cloud infrastructure (AWS)
Specific client names, team size, and business metrics are internal to Signovate and are not published here.
04 · Projects
Engineering case studies, not screenshots
Each project below breaks down the problem, the architecture, and the decisions behind it.
Backend / Distributed Systems
Algorithmic Trading Platform
Event-driven order processing over Kafka, built for correctness under concurrency.
Backend / API Design
Digital Wallet Platform
A layered Spring Boot service modeling wallet balances, status, and ownership.
Full-Stack / Real-Time Systems
Cricket Player Booking Platform
Full-stack, real-time booking across players, ground managers, and owners.
Computer Vision / Applied AI
Smart Surveillance System
Multi-camera detection and tracking with YOLOv8, built as an applied computer-vision project.
03 · Skills
A backend-weighted toolkit
Grouped by how central each area is to Akash's day-to-day work — not an alphabetical dump.
Core Backend
coreMessaging & Distributed Systems
coreDatabases
coreSecurity
Cloud & Infrastructure
Testing
Observability & Operations
API & Dev Tools
Frontend & Full Stack & Languages
05 · Engineering Principles
How I think about software
Boundaries before code
Before writing a service, decide what it owns and what it explicitly doesn't. Most painful coupling later traces back to a boundary that was never actually drawn.
Observability is part of the feature
A service isn't done when it handles the happy path — it's done when you can tell, from logs and metrics, why it failed at 3am without reading the code.
Async by default at the seams
Anywhere two services meet, prefer an event over a synchronous call unless there's a real reason for a blocking dependency. It's easier to add synchronicity later than to remove it.
Tests describe intent, not implementation
A good test should survive a refactor. If changing internals breaks tests that never touched the behavior being changed, the tests were coupled to the wrong thing.
Data models outlive the code around them
Schemas and message formats are the hardest thing to change in a running system. Worth spending real time on before the first migration ships.
Debugging is a skill, not a fallback
Reproducing an issue reliably before touching code is usually faster than guessing — even when guessing feels faster in the moment.
06 · Contact
Have a backend problem worth solving?
Open to backend / Java / Spring Boot roles. The fastest way to reach me is email — happy to walk through any project on this site in more depth.