My Projects

Website - [You are here!]

I decided to create a website so that I could share my knowledge and experience with other people, as well as being a great place to store my projects and have a blog!

Project links:

Source Code · Demonstration

Technologies used:

Rinha de Backend 2024/01 - Race condition with Financial operations

Rinha de Backend is a brazillian challenge whose main objective is to share knowledge in the form of a challenge! This was the second edition where the main topic was concurrency control with credit and debit financial operations

Project links:

Source Code

Technologies used:

Adoção Cãosciente - [SSC0536 - Design and Development of Information Systems]

Platform for automating animal adoption processes, including registering animals, users, adoption forms, etc.

Project links:

Source Code · Demonstration

Technologies used:

Formula 1 - [SCC0541 - Databases Laboratory]

Complete system with queries and queries for a real Formula 1 database, including data on races, drivers, teams, etc.

Project links:

Source Code

Technologies used:

Caaso Eletroniks - [SCC0560 - Human-Computer Interaction and User Experience]

Website for a fictitious electronics store with a focus on usability and user experience, including prototyping and usability testing.

Project links:

Source Code · Demonstration · Figma

Technologies used:

Website - [You are here!]

What problem does this project solve?

The problem that this project solves is the need for a place to share my knowledge and experience, as well as showing my profile as a developer through my projects and skills.

How it was developed

The development was done using Jekyll, a static site generator, and hosted on GitHub Pages. The site is responsive and uses HTML5, CSS3 and JavaScript. The content is written in Markdown and the site is versioned on GitHub, in addition to using GitHub Actions to automate the deployment of the site on GitHub Pages, I purchased a domain and configured the DNS to point to GitHub Pages.

Why these technologies?

Nowadays it's more common to use frameworks like React, Vue or Angular to create websites, but I decided to use Jekyll because it's a static site generator, which means the site is faster and more secure, as well as being cheaper to host. In addition, Jekyll is very easy to use and has a very active community.

What I learned

Several lessons have already been learned with this project, from setting up a domain and DNS, to creating a blog with Jekyll and using GitHub Actions to automate the deployment of the site. I've had a lot of problems and I've learned a lot from them too, always looking for the best solution for each problem.

Next steps

There are several next steps for this project, such as allowing the user to switch between light and night mode, among several usability and accessibility improvements, as well as adding new content and features to the site.

Rinha de Backend 2024/01 - Race condition with Financial operations

What problem does this project solve?

Not exactly a real problem, but a challenge within the dev community. Rinha de Backend is a challenge organized by Francisco Zanfranceschi (@zanfranceschi) and its main objective is to develop an API with a focus on architecture and optimization in resource-limited scenarios. In this competition, resources were limited so as not to exceed 1.5 CPU units and 550MB of memory between all the components of the architecture. This was the second edition of the competition and the challenge was about competition with financial operations.

How it was developed

This challenge was solved using the Go language using the Fiber framework (w/ fasthttp), a PostgreSQL database and Ngix as a reverse proxy. The project was dockerized to facilitate execution within a controlled environment and to facilitate load testing. Gatling was used for the load tests. The project took me about a month to develop so that it would perform well within the competition. To deal with concurrency issues and guarantee data integrity, I used the Pessimistic Lock technique within postgres. The architecture of the project was designed to be scalable and performant, and within the scenario of limited resources and the issue of competition, the use of caching was not necessary, but the concept of pooling connections to the database was used.

Why these technologies?

Golang is one of today's most performant programming languages and is widely used in highly competitive scenarios, as well as being very simple and easy to learn. Fiber is a very performant and easy-to-use web framework, as well as being very fast and having a very active community. PostgreSQL is one of the most widely used databases in the world because of its robustness. Gatling and Nginx were pre-selected tools within the rules of the competition for the load test

What I learned

This challenge was something beyond my comfort zone and it was great to have completed it, I learned a lot interacting in the community and I made a lot of mistakes too, I believe the biggest challenge was to find the main performance bottleneck and optimize it, fortunately I managed to find and optimize the problem. I learned a lot about concurrency and architecture optimization with this challenge.

Next steps

the rinha was finished meeting all the requirements and without any penalties I got the maximum grade, what is missing for this project would be the addition of tests to ensure the integrity of the system in cases of adding new features. Another point would be to develop the rinha in other technology stacks to learn more about other languages and frameworks.

Adoção Cãosciente - [SSC0536 - Design and Development of Information Systems]

What problem does this project solve?

An NGO can receive many animals and many adoption requests, and the adoption process can be very bureaucratic and time-consuming, so the platform solves the problem of automating animal adoption processes.

How it was developed

The project was developed during a final course in Software Engineering at the University. The Frontend was built using React and Typescript as well as TailwindCSS using the NextUI library, the entire folder structure follows Clean Architecture. The Backend was built using Python FastAPI and MongoDB, and was dockerized to facilitate deployment. In addition, integration and e2e tests were carried out with Cypress.io. All these technologies and functionalities were done by a team of 8 people.

Why these technologies?

In addition to the team's common knowledge, the choice of technologies was made with scalability and ease of maintenance in mind, as well as being modern technologies with an active community.

What I learned

My role in this project was as Scrum Master and Backend Developer, I learned a lot about leadership and project management, as well as learning new technologies and software development practices.

Next steps

My role in this project was as Scrum Master and Backend Developer, I learned a lot about leadership and project management, as well as learning new technologies and software development practices.

Formula 1 - [SCC0541 - Databases Laboratory]

What problem does this project solve?

There is a huge amount of data about Formula 1, and it would be very difficult to analyze and understand this data without a system that facilitates the visualization and manipulation of this data. The system solves the problem of visualizing and manipulating Formula 1 data.

How it was developed

The development was done during a Database Laboratory course at the University. The Backend was built using Python Flask and PostgreSQL, Docker was used to simulate the PostgreSQL database. The Frontend was done using HTML5 and CSS3 with Jinja2, which is the standard used by Flask. The whole project was done in a very simple way, because the focus of the project was the database and the queries.

Why these technologies?

The choice of technologies was made with simplicity and ease of use in mind, Python is highly used for data manipulation and Flask is a very simple and easy to use web framework, as well as being very quick to prototype and test ideas. PostgreSQL was the database used for most of the course, and Docker was used to facilitate database simulation. Finally, the reason for not creating a separate frontend with some SPA framework was precisely to focus on the database and the queries, and not on the frontend itself.

What I learned

I learned a lot about databases with this project, from modeling the database to creating complex queries. Some of the main database concepts used to create the project were Windows Functions, PGSQL, Views, Triggers, Indices, Stored Procedures and Functions.

Next steps

The whole project was done in about a week and a half (course deadline), so several decisions were made to simplify the project, such as the example of not creating a separate frontend. Another point is the backend code, which could be improved and modularized following good practices and design standards. In addition, the project could be drastically improved with the addition of a more complete and interactive frontend for data visualization and manipulation.

Caaso Eletroniks - [SCC0560 - Human-Computer Interaction and User Experience]

What problem does this project solve?

This project does not actually solve a problem, but rather a challenge proposed by the Human-Computer Interaction and User Experience course, which was to create an e-commerce-themed website with a focus on usability and user experience, including prototyping and usability testing.

How it was developed

The project went through several stages of Design Thinking, from market research and personas, there was prototyping at the 3 levels (low, medium and high fidelity), and finally, the development of the website. The frontend was built using React and Typescript, and MaterialUI. The project was hosted on GitHub Pages for free.

Why these technologies?

React was the technology of the moment at the time, and MaterialUI was the library chosen due to the large number of research and usability tests that showed that Material Design is very efficient for usability and user experience, as well as being beautiful and modern. Typescript was chosen to guarantee the quality of the code and facilitate future maintenance of the project.

What I learned

In this project I did one of my first deployments of a website using GitHub Pages, and I learned a lot about website responsiveness and about usability and user experience thanks to discipline and how important accessibility is in software systems.

Next steps

The next steps for this project would be to create a backend to simulate real e-commerce, and add more features and interactivity to the website, because given the focus of the project, only the happy path to purchase was made, and no error paths or user interaction with the system were mapped. In addition, the project could be improved by adding usability and accessibility tests, and by adding more features and interactivity to the website.