Ecosistemas
Software Engineer
Assigned to AGEA (Clarín Group), working on microservices and the gradual migration of on-premise infrastructure to Google Cloud. Supporting cloud configuration and application adaptation.
Electronic engineer and Java backend developer. I build APIs, connect REST and SOAP systems, and modernize applications for cloud environments. Experience across ERP, logistics and media platforms.
Assigned to AGEA (Clarín Group), working on microservices and the gradual migration of on-premise infrastructure to Google Cloud. Supporting cloud configuration and application adaptation.
Developed Java microservices for ERP and logistics platforms, real-time WebSocket communication in Tomcat, and containerization of legacy services. Supported Linux servers and CI/CD workflows.
Researched and built a web chatbot with Python and Rasa, deployed on Google Cloud. Created a Flask and PostgreSQL web tool to manage bot training.
A Java and Spring Boot payment API exploring reliable payment processing. The repository includes PostgreSQL persistence, authentication, Docker Compose, health checks, OpenAPI documentation and security design notes.
The design separates a failed payment from an unknown result. A timeout requires reconciliation before another charge. Idempotency keeps repeated requests tied to the same operation. This is a learning project, with no production payment processing.
Exploring an applied robotics venture in Rosario, starting with maintenance and repair for domestic robot vacuums. Currently researching local demand and service feasibility.
Share the model, issue and city. Inquiries help assess demand and feasibility; service availability is confirmed individually.
SecurePay · Design case from a personal learning project.
A payment provider may process a charge even if its response arrives too late. Creating a new charge after a timeout can produce a duplicate payment.
Use an idempotency key to identify the request. Keep an uncertain outcome pending, then reconcile with the provider before deciding whether another attempt is safe.
Check repeated requests, concurrent retries and delayed confirmations. The target is one recorded operation and consistent responses for the same key. These are acceptance criteria, not published test results.
Next milestone: demonstrate these scenarios with repeatable tests. No production payment processing or measured production outcomes are claimed.
An initial diagnostic for teams dealing with integration issues or planning to modernize an existing application.
We start with one application or integration and a specific problem: failed requests, retries, communication between systems, or deployment obstacles.
Discuss my systemScope, timing and fees are agreed before starting.
Universidad Nacional de Rosario · FCEIA · 2011–2019
Spanish: native · English: A2, progressing toward B1