alindgren / fundraise Goto Github PK

Use RabbitMQ or Azure Queue Storage to queue a message send.

Use case 1: A donor signs up to pay $10/month until cancelled.
Use case 2: A donor pledges $120 dollars paid $10/month (ends after 12 months).

Depend on Stripe to process the recurring payment and handle a webhook to update donor records.

https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/background-tasks-with-ihostedservice

See https://msdn.microsoft.com/en-us/magazine/mt694089.aspx and https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging

Currently iterating through each donation to set the FundraiserName and loading the Fundraiser entity for each donation. See https://github.com/alindgren/Fundraise/blob/master/Fundraise.MvcExample/Controllers/ProfileController.cs#L40-L48

The original idea was to track changes to donations but maybe could be done in a more generic way for changes to all entities -- perhaps loosely model it after Stripe's events.

Create events in Fundraise.RequestHandlers.InProcess and add event handlers that the application (MVC Example web app), can use to create and publish the IntegrationEvents.

While at it, fix the namespace for DonateHandler.cs.

Related Links:

• https://developers.google.com/web/fundamentals/payments/
• https://github.com/GoogleChrome/appr-wrapper
• https://developer.apple.com/documentation/applepayjs
• https://stripe.com/elements
• https://stripe.com/apple-pay

Need to come up with an architecture for this. Would be great if there was a third party library to deal with sending emails using templates and various services.

See https://jonhilton.net/2016/06/06/simplify-your-controllers-with-the-command-pattern-and-mediatr/

Create nuget packages for:

• Fundraise.Core
• Fundraise.IntegrationEvents
• Fundraise.IntegrationEvents.RabbitMQ
• Fundraise.Requests
• Fundraise.RequestHandlers.InProcess (rename to to just Fundraise.RequestHandlers?)

Also, possibly move Fundraise.MvcExample (and Tests) to a separate repo.

We can update donations if there is a refund.

The core unit tests use EF Core's InMemoryDatabase for testing, but that does not seem to be possible with the MVC example site (specifically the Identity DB context). So the MVC Example site is running using LocalDB. While the database is not committed to the repo, it does not get recreated each time the site runs, or when the Selenium tests run, so tests could fail after the first time it is run (without manually removing the old database). Not sure the best way to solve this problem...

This expands the scope of the project, but the idea is to create a system for tracking Donors. Need to figure out how this would relate/differ from a user system (ASP.NET Identity).

Perhaps use RabbitMQ? https://www.rabbitmq.com/

Check out https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/