Flexbase
Search…
Flexbase
Introduction
#JoyofCoding with Flexbase
Core Concepts
Thinking in Flexbase
Sample Application
Solution Structure
Introduction
Input Output Models
Messages
Domain
Pre Bus
Post Bus
Subscribers
Bus Gamma
Persistence
Hosting
Startup Code - WebAPI
Startup Code - Background Job
Endpoint - AppSettings
Bridge
Basic CRUD - Insert & Update
Introduction
View Generated API Definition in Swagger
Walkthrough Generated Code Insert
Walkthrough Generated Code Query GetById
Domain Model
Migration
AppSettings
Bus : How Basic Routing Config Works
INSERT : Input API Model
INSERT : Attribute Validation
INSERT : Plugin Validation
INSERT : Mapper
INSERT : Controller
INSERT : Services
INSERT : PostBus Handler
INSERT : PostBus Subscriber
INSERT : Demo In Action
QUERY : Output API Model
QUERY : Build and Fetch Pattern
QUERY : Demo In Action
Basic CRUD 2
Introduction
View Generated API Definition In Swagger
Walkthrough Generated Code Update
Walkthrough Generated Code Delete
Walkthrough Generated Code GetList
Walkthrough Generated Code Get Paged List
Update In Action
Delete In Action
GetList In Action
GetPagedList In Action
Konarch
Powered By GitBook
Post Bus
Flexbase Solution Structure
The Postbus can be found in two different projects in the Orchestration layer. The first one is Handlers.Default.BusGamma and the second one is the Handlers.Default.Plugins.
The BusGamma is specific to NserviceBus implementation. This handles the request put in the bus in the PreBus layer. Separation of BusGamma handlers and execution of actual business code into Plugins help to keep the bus code decoupled and helps to change or swap the bus whenever needed.
In the PreBus the command is put in the bus after processing the validation and the handler further processes that from the queue. This helps in separation of concern and all the actual business logic resides in the plugins..
​
Previous
Pre Bus
Next
Subscribers
Last modified 1yr ago
Copy link