Backupator - Solution for automatic backups

I have had a harrowing experience with a ransomware attack and it has left a deep impression on me. Back in 2020, I was a victim of a cyber attack that impacted my server and left me devastated. However, I was lucky enough to have taken a precautionary measure before the attack occurred. Six months prior to the attack, I had reinstalled my system and split my database into two drives, one being the C:/ drive and the other being the D:/ drive.

When the pandemic hit, I exposed my server to allow remote access to the system. Little did I know, I was being targeted by a ransomware attack. I noticed strange activity on my server, when my mouse started moving on its own. I quickly shut down the connection and rushed to the office to see the damage. Unfortunately, my C:/ files were completely ruined and I had no backup. But, to my surprise, my D:/ drive was left untouched.

This was a hard-learned lesson for me and I realized the importance of having a backup. I then decided to create an application that would regularly backup my database and send it to another server via FTP. The application has been working perfectly since December 2022 and I now have daily backups that I can rely on.

If you're someone who has faced a similar experience, or would like to avoid one, I would be happy to sell you a copy of my application and even configure it for you. Alternatively, if you're impressed by my story, I would be delighted to offer my services as a solution for your office.

Kubernetes - Kafka real estate attempt

Somewhere in the second quarter of 2022 we were committed to make a microserve architecture Reservation system like airbnb.

the services were Payment, Paypal, Credit, Bank, Property, Account, Notification (at my charge), Authentication, property-rental-web I configured kafka as a central queue messaging system in order to manage the communication between the pods that were deployed in kubernetes, this architectural approach helps us to loosely coupled the services between them, so they have the advantage of being easily configurable, monitorable, and if a service is added or deleted from the cluster the microservice is not responsible for the communication in between.

Our project included supported services that run perfectly with kafka, like the Cassandra database, which can be easily escalable in terms of architecture. redis to cache responses of data, zipkin for tracing our requests, and responses.

I like how this project architecturally was well oriented, giving a high, reliable and big scalable application that can rely heavily on microservices.

After this I am pursing my kafka certification with confluent.

Task Management System

This system relies on a central ticketing system that is based on email.

I created the software from scratch and it follows best practices in programming.

The system centralizes all queries and tasks into a single responsible gateway, which then assigns the tasks to workers who are active.

Users can submit tasks only via email, providing a simple channel for running tasks.

The system includes monitoring features, allowing managers to monitor the number of tasks generated by each worker and the state of each task.

The state of a task is critical for tracking its progress and determining if further action is needed.

The system uses an SQL-server database and stores information on an IIS server.

The effective management of archives makes it an ideal solution, as it provides complete history of tasks processed so far. The system also includes a powerful search function implemented in JavaScript that enables easy filtering of tasks.

It can be deployed with an API for monitoring and interacting with tasks, including tracking metrics in real-time.
This is an example of the monitoring TV