Forem: Alejandro Tacoronte González

Building a Movie Recommendation API with Spring Boot 🎬

Alejandro Tacoronte González — Sat, 14 Mar 2026 12:30:09 +0000

Recently I built a backend API for a movie and TV show recommendation platform using Java and Spring Boot.

The goal of the project was to practice designing a REST API, implementing authentication, and integrating an external API.

Features

The API includes several features:

Search movies and TV shows using the TMDB API
User authentication with JWT
Save favorite movies and shows
Rate content
Get trending content
RESTful API design
API documentation using Swagger / OpenAPI

Tech Stack

Backend

Java 21
Spring Boot
Spring Security
JWT Authentication
Spring Data JPA

Database

PostgreSQL

External API

TMDB API (The Movie Database)

Documentation

Swagger / OpenAPI

Example API Request

Example request to get trending content:

GET /content/trending

Example response:

{
  "page": 1,
  "results": [
    {
      "title": "War Machine",
      "release_date": "2026-02-12",
      "vote_average": 7.1
    }
  ]
}

Project Architecture

The application follows a layered architecture:

Controller → Service → Repository → Database

This structure helps keep the code organized and maintainable.

API Documentation

The API is documented using Swagger / OpenAPI, which makes it easy to explore and test the endpoints.

What I learned

While building this project I practiced several backend concepts:

Designing REST APIs
Implementing authentication with Spring Security
Using JWT for authorization
Integrating external APIs
Structuring a backend project using layered architecture

GitHub Repository

You can find the full project here:

https://github.com/alejandrotg-code/tv-and-movie-db

Feedback and suggestions are always welcome!

My first contribution to an OpenSearch project: A Junior’s journey 🚀

Alejandro Tacoronte González — Sat, 28 Feb 2026 12:30:42 +0000

🇺🇸 English Version

How it started

Hello world! I'm Alejandro, a Junior Developer currently studying AI & Big Data. Like many beginners, I used to look at huge GitHub repositories (like those from Amazon or the Linux Foundation) with a mix of respect and fear. I thought: "I'm not ready to contribute there yet."

I was wrong.

Yesterday, I made my first contribution to the opensearch-agent-server project, managed by Mingshi Liu (@mingshl), a Machine Learning Engineer at AWS OpenSearch.

It's not "just" a license

My task was to add the Apache 2.0 LICENSE file. You might think: "That's not coding!". But for a Junior, this was a masterclass in professional workflows:

Reading the Guidelines: I had to study the CONTRIBUTING.md file.
DCO (Developer Certificate of Origin): I learned that big companies require signed commits (git commit -s) for legal safety.
Communication: I had to interact in English with a Senior Engineer to get the task assigned.

The feeling

Seeing an engineer from Amazon say "thanks for taking the initiative" and seeing my name in the "Assigned" section was a huge boost for my confidence.

My advice for Juniors: Don't wait to be a Senior to contribute. Start with documentation, licenses, or small fixes. The community is waiting for you!

🇪🇸 Versión en Español

Cómo empezó todo

¡Hola a todos! Soy Alejandro, un desarrollador Junior estudiante de IA y Big Data. Como muchos principiantes, solía mirar los grandes repositorios de GitHub (como los de Amazon o la Fundación Linux) con una mezcla de respeto y miedo. Pensaba: "Todavía no estoy listo para contribuir ahí".

Estaba equivocado.

Ayer hice mi primera contribución al proyecto opensearch-agent-server, gestionado por Mingshi Liu (@mingshl), ingeniera de Machine Learning en AWS OpenSearch.

No es "solo" una licencia

Mi tarea fue añadir el archivo Apache 2.0 LICENSE. Podrías pensar: "¡Eso no es programar!". Pero para un Junior, esto fue una clase magistral de flujos de trabajo profesionales:

Leer las reglas: Tuve que estudiar el archivo CONTRIBUTING.md.
DCO (Developer Certificate of Origin): Aprendí que las grandes empresas exigen commits firmados (git commit -s) por seguridad legal.
Comunicación: Tuve que interactuar en inglés con una ingeniera Senior para que me asignaran la tarea.

La sensación

Ver a una ingeniera de Amazon decir "gracias por tomar la iniciativa" y ver mi nombre en la sección de "Asignado" fue un subidón de confianza increíble.

Mi consejo para otros Juniors: No esperes a ser Senior para contribuir. Empieza con documentación, licencias o errores pequeños. ¡La comunidad te está esperando!

Let's connect! / ¡Conectemos!

GitHub: alejandrotg-code
LinkedIn: https://www.linkedin.com/in/alejandrotacoronte/

Looking for Advice as a Junior Fullstack Developer

Alejandro Tacoronte González — Mon, 17 Nov 2025 18:50:08 +0000

Looking for Advice as a Junior Fullstack Developer (Java, Node.js, React)

Hi everyone 👋,

My name is Alejandro Tacoronte, and I completed my (Cross-Platform Application Development) studies in 2024. I’m currently looking to grow as a junior fullstack developer and would love to get advice from those with experience in the industry.

I have experience and knowledge in:

Backend: Java and Node.js
Frontend: Some experience with React
Databases: SQL
Version Control: Git

I’ve worked on projects during my studies and internships, and now I want to build my own projects that demonstrate my skills and ability to learn.

💡 I’d love to ask the community:

What “mini projects” would you recommend for a junior fullstack developer to stand out?
Which technologies or frameworks are most relevant in 2025?
Any advice on how to showcase skills effectively, even without years of professional experience?

I’d greatly appreciate any tips, resources, or personal experiences. 🙏

Thanks for reading! I’m looking forward to sharing my progress and learning alongside you all.