dotnet-microservice-template

Inspiration

Give .net stacks some love

What it does

Flow User registers and logs in and makes a reservation via frontend Reservation is sent to backend API Backend API save reservation to the database Backend API sends a reservation completion notice to a queue (RabbitMQ) A console application listens to new messages on queue. On message received, it sends an SMS notifying user that reservation has been successful

How we built it

.net 7 web api, .net 7 web app, sql, rabbitmq, .net 7 console app (STACK)

Challenges we ran into

Inability to get https endpoints up and running on bunnyshell for .net7

Accomplishments that we're proud of

Containerizing dotnet applications in a flexible manner by leveraging environment variables to dynamically configure applications via orchestration tools (docker-compose & Kubernetes).
Orchestrating a full stack of applications to communicate seamlessly with each other and obey application startup precedence

What we learned

Garnering a deeper understanding of what it takes for microservices to successfully work in tandem with each other.
Understanding the need to make container applications cloud-ready by ensuring HTTPS has been enabled and configured
Gaining a deeper appreciation of templating and its importance. Templating makes applications easier to deploy at a rapid cadence with high reliability and consistency of functionality.