Real-world software design practices when developing ASP.NET web systems by Bojan Veljanovski

Ready

Bojan Veljanovski

Software Development Engineer | Technical Architect

HASELT

Real-world software design practices when developing ASP.NET web systems

Ready

General Sponsors

Platinum Sponsors

Silver Sponsors

Gold Sponsors

Bronze Sponsors

Promoters

Ready

A quick chat

• Users interact with apps by INTENT

• Server processes ACTIONS

• Who triggers those ACTIONS?

Ready

Example of User Intent in medical institution

• Actor: Patient

– Request an appointment with the doctor

– Cancel appointment

– Re-schedule appointment

• Actor: Doctor

– Confirm requested patient’s appointment

– Deny requested patient’s appointment

– Check schedule

– Look into historical medical records for the patient

Ready

Example of a System Action

• Patient Actions

– RequestNewAppointment

– CancelRequestedAppointment

– RequestAppointmentReschedule

• Doctor Actions

– ConfirmRequestedAppointment

– DenyRequestedAppointment

– GetSchedule

– GetHistoricalRecordsForPatient

Ready


• Patient Actions




• Doctor Actions



– GetSchedule


• WRITE

• WRITE

• WRITE

• WRITE

• WRITE

• READ

• READ

Ready


• Patient Actions




• Doctor Actions



– GetSchedule


• Command

• Command

• Command

• Command

• Command

• Query

• Query

Ready

Users work with apps by INTENT.

Your UI should capture it!Your system should process it!

Evolving Architecture

Ready

Agenda

• Evolving Architectures

• Command & Query Implementation

• Component Oriented Single Page Modules

• Evolutionary database development

• Summary

Ready

Bojan Veljanovski

• Software Development Engineer and Technical Architectat HASELT

• HyperLAB Coordinator

• Technical Speaker

• Microsoft Certified Professional

• Former Microsoft Student Partner

Favorite topics:

– Software Architectures and Design

– Code. Code. Code.

– Emerging technologies

Ready

Evolving Architectures(from high-level perspective)

Ready

Classical Layered Architecture


UI

ASP.NET

App Services

Data Access Logic

DB

DTO

DTO

Domain Object

Data Structure

ValidationBusiness LogicData ReadsData Writes

Ready

Adding Query


UI

ASP.NET

App Services

Data Access Logic

DB

DTO

DTO

Domain Object

Data Structure

ValidationBusiness LogicSome Data ReadsData Writes

Query Handler

Data Reads

Query Result

Domain Object

Ready

Going further with the Query


UI

ASP.NET

App Services

Data Access Logic

DB

DTO

DTO

Domain Object

Data Structure

ValidationBusiness LogicSome Data ReadsData Writes

Query Handler

Query Result

Denorm Structure

Data Reads

Ready

Adding Command


UI

ASP.NET

App Services

Data Access Logic

DB

DTO

DTO

Domain Object

Data Structure

ValidationBusiness LogicSome ReadsWrites

Query Handler

Query Result

Denorm Structure

Data ReadsCommand

Handler

Command

Domain Object

Ready

Some cleaning


UI

ASP.NET

Data Access Logic

DB

Data Structure


Query Handler

Query Result

Denorm Structure

Data ReadsCommand

Handler

Command

Domain Object

Ready

Some cleaning


UI

ASP.NET

Data Access Logic

DB

Data Structure


Query Handler

Query Result

Denorm Structure

Data ReadsCommand

Handler

Command

Domain Object

CommandQuery Result

Ready

What about collaborative systems, real-time and stuff?


Ready

Look ma’, real-time


UI

ASP.NET

DAL

DB

Query Handler

Command Handler

Event HandlerEvent

Socket: PUSH

Ready

Full-Featured CQRS (overview)


Ready

Command & QueryImplementation

Command & Query Implementation

ReadyReady

Demo:Implementing CQS

Ready

Component Oriented Single Page Modules

Ready

Common seen SPA structure

• Controllers

• Models

• ViewModels

• Views

• Modules

• Components

• Utils

• Services


Ready

There is a better way

• Modules

• Components

– View

– ViewModel

• Shared

– Events (message constant)

– Actions (message constant)

– MessageBus (pub/sub)

• Data Services

– API Calls

– LocalStorage


Ready

Rules of thumb

• One Module per Page

• Focused modules

• Cohesive components

– Not *everything* should be reusable

• Components don’t TALK they:

– REACT (to messages)

– EMIT (messages)

• Message types

– Event

– Action


Ready


MessageBus

Data Services

API

Module A

Module B

Module C

pub

sub

pub

sub

pub

sub

Ready

Flux Architecture


ReadyReady

DemoCOSPM

Ready

Evolutionary Database Development

Ready

Evolutionary Database Development• A DB consist of Schema and Test Data

• Schema is Source Code

• Schema changes are tracked over-time

• Version it in GIT

• Every dev gets its own db instance

• Devs make frequent integrations into shared master

db

• FluentMigration mechanisms help us build our db in

any RDMS system we want

Evolutionary Database Development

ReadyReady

DemoFluent Migration

Ready

Summary

• Users work with apps by INTENT

• System processes ACTION triggered by INTENT

• READS are different from WRITES

– Treat them as so, in your code, yo

• Components are simple, inter-components communication is hard

• Database schema is source code too – it evolves

– Version it

• Don’t fall into the tech hype hole

– Think

• There are no ‘best practices’, only ‘good practices in context’

ReadyReady

Complete the evaluation and earn the chance to win valuable prizes from our sponsors

Questions

ReadyReady

Thank you

Real-world software design practices when developing ASP.NET web systems by Bojan Veljanovski

Technology

product names

informational purposes

market conditions

patient ready

example of user intent

patients appointmentdeny

medical institutionactor

historical medical records