Tools
Stack & tools
Technologies I use in real production projects. Not exhaustive — only what I actually ship to production regularly.
Frontend & UI
Primary framework for enterprise application frontends. Quasar provides a complete component system with SPA/SSR/PWA support without extra configuration.
For projects that require a stricter, more typed frontend architecture. Nebular extends Angular with UI components ready for dashboards and admin panels.
In projects where the team or client requires it. Functional components with hooks, without heavy frameworks on top.
For content sites and portfolios like this one. Islands Architecture, zero JS by default, and exceptional Core Web Vitals performance.
Utility-first CSS for all frontend projects. Eliminates friction of custom CSS and maintains visual consistency effortlessly.
Backend & Languages
Primary stack for backend projects. Mature ecosystem, excellent ORM, and Eloquent for day-to-day use.
For systems with high load, microservices and enterprise clients. Spring Security and JPA cover 90% of cases.
Secondary APIs, scripts and automation tools. I prefer pure backend TS without heavy frameworks.
Processing scripts, infrastructure automation and data tasks when the ecosystem justifies it.
Databases
First choice for almost everything. JSONB, arrays, native full-text search. The most complete tool in the relational ecosystem.
Cache, sessions, rate limiting and lightweight queues. Essential in any system with real load.
In projects where it already exists or when the client requires it. Well configured with InnoDB it is perfectly valid. MariaDB in contexts where Galera Cluster compatibility is needed.
Full-text search, logs and analytics. Powerful but expensive to operate — only when there is a clear use case.
Infrastructure & Cloud
The provider I use most. ECS Fargate for containers without managing instances, RDS for managed databases.
Everything as code. Reusable modules, workspaces per environment, remote state in S3 + DynamoDB for locks.
Dev, staging and prod in the same container. Compose for local, ECS for production.
Primary CI/CD. Tests, linting, Docker image build and automated deploy to ECS on every push to main.
Reverse proxy, TLS termination, security header configuration. The faithful production companion.
Messaging & Queues
For asynchronous communication between services, with message routing, dead letter queues and manual acknowledgements.
When the system is already on AWS and doesn't need RabbitMQ's advanced routing. Simple, scalable and managed.
For workers in Laravel on Redis or SQS. Horizon gives complete visibility of queues in production.
Development tools
JetBrains IDEs. Indispensable for refactoring, code navigation and debugging in Java and PHP.
For TypeScript, Python, Terraform editing and markdown. Lightweight and extensible.
GUI for databases. Much faster than pgAdmin for exploration and quick queries.
API testing. Insomnia for complex projects with environments, HTTPie for quick terminal tests.
Version control. Conventional Commits, PRs with reviews, and branch protection on main.
Monitoring & Observability
Logs, metrics and alerts when everything is on AWS. Log Insights for ad hoc queries.
Error tracking in production. The stack trace with context is essential for diagnosing bugs quickly.
In clients that have it. APM and real-time infrastructure metrics.
This page is updated with the actual stack I use in current projects. Some technologies change over time — the choice always depends on the problem, not the trend.