Objetivo

Este Projeto tem o objetivo de exemplificar o uso de diversas tecnologias e padrões diferentes aplicados tanto no backend como frontend.

Tecnologias aplicadas e Acesso

The project was developed in angular, nextjs, blazor and blazorwasm on the frontend, and blazorwasm can be installed on a cell phone. Backend developed in dotnet with all authentication services and nodejs without authentication services (test).

To access:

• user: 1@1
• password: 12345

Links:

• Blazor: https://webappscheduleblazor-gnfzcfeca0dbbnbp.brazilsouth-01.azurewebsites.net/login
• Blazor WASM: https://schedule-dotnet-app-client-blazorwasm-72jl.vercel.app
• Angular: https://schedule-angular-app-client.vercel.app/login
• Nextjs: https://schedule-nextjs-app-client.vercel.app/signin

Tecnologias aplicadas

This is prototype using follow tecnologies:

• BACKEND

• API DOTNET

  • Hosted in Azure
  • Using following tecnologies and patterns:
  • Entity
  • JWT
  • Mapper
  • Fluent
  • DDD / SOLID

• API NODEJS

  • Hosted in vercel
  • CI/CD implemente with GITHUB
  • Using following tecnologies and patterns:
  • Prisma
  • DDD / SOLID

• DATABASE

  • Mysql Hosted in TargetHost

• FRONEND

• Blazor Server,

  • Hosted in Azure
  • CI/CD implemente with GITHUB

• Blazor WASM

  • Hosted in vercel
  • CI/CD implemente with GITHUB

• Nextjs

  • Hosted in vercel
  • CI/CD implemente with GITHUB

• Angular

  • Hosted in vercel
  • CI/CD implemente with GITHUB

Descrição

This is a simple project to demonstrate some of my knowledge applied to different technologies. It is a prototype application for scheduling services. Current steps for scheduling:

1. Create a professional
2. Create a service
3. Create a professional and service schedule
4. Schedule the service for the customer
5. Confirm or cancel the service if it was provided or not

Next steps to be implemented:

1. Generate billing and service cost
2. Function to create a service without scheduling
3. Create a separate schedule unlinked to the professional's schedule