RIZIV / INAMI : GenPay

GenPay

Why:
Communication with the Finance Application, Creation of the Payment orders to the Bank, Processing Bank Responses are all actions we don't want every application that offers payments to reinvent every time.
This project is the transversal communication platform that processes and does the follow-up of all payments that are delivered.

My Work

• Architectural design application and communication design
• Communication with Lead Developer about which components/Frameworks to use 
• Assistance Setup Local TFS for Deploy
• Assistance Setup Local IIS for Deploy

Application Architecture Layers

• 2 FrontEnds ( FrontOffice external and BackOffice internal ) 
• API layer for Communication between the FrontEnds en de BackEnds
• We have 3 big Bounded Contexts for 3 MicroServices
  • Fiscal Documents
  • Payments
  • Reference Data  
• The back End will have multiple MicroServices for the business Steps in the Payments Context
  • for every step in the workflow there is a MicroService so we can easily swap version/implementation 
  • we use a Choreographic coordinated Saga Setup for the MicroServices 
• We have 3 big Bounded Contexts 
  • Fiscal Documents
  • Payments
  • Reference Data

Health Setup

• Health Checks [ Dependency checks ] for It Support.
• Probe [ HealthChecks = OK => 200 ] for Load Balancer.
• StatePage [Watchdog ] for Dev-Users to see detailed statuses of all parts in the whole workflow ( api's, bus, services, UI's, databases, external dependencies)

Components / Frameworks / Technology

• Front Ends will be MVC  pages using Razor ( Enterprise Architectural ) : .Net 5 
• API layer will be Web Api - .Net 5
• MicroServices will be build in .Net 5 
  • Web Api
  • Container Ready for deployment in multiple environments
  • Nuget packages will be created for use by external parties
• Choreographic WorkFlow will be setup using nServiceBus using the API approach, so we can add Event Sourcing easy when Riziv sets up an Enterprise Event Store

Initial Issues (december 2020)

• we'll start using Net Core 3.1 
  • nServiceBus version for .Net 5 is not yet ready
  • .Net Core 3.1 let's us use all other components and demands

Issues Update (March 2021) 

• nServiceBus
  • nServiceBus has now version for .Net 5 => we start using .Net 5
• Containers 
  • Riziv is still working on Container deployment environment

Issues Update (June 2021)

• Net 5
  • Riziv Health nugget : We need to upgrade it to .Net 5
• OAuth
  • Still no progress
• Containers
  • Still no progress
• POC 
  • Ready for start development of Project Code
• Analyses ( US) 
  • Not far enough to start Project development 
• S&S
  • Still not all infra ready