C S L a - Data Access Layers

Cathoy says business logic will survive tearing off and replacing the u i. Architecture recommends data access code is isolated in its own layer, so that when you have to switch from o entity framework five to entity framework six - you don't have to rewrite all your business logic.

Transcript

chevron_right

Play full episode

chevron_right

Transcript

Episode notes

Rockford Lhotka is the creator of the widely used CSLA .NET open-source development framework. He is the author of numerous books and regularly speaks at major conferences around the world. Rockford is a Microsoft Regional Director and MVP. He is co-chair of Visual Studio Live!, and the chair of the Cloud & Containers Live! Conferences. Rockford has worked on many projects in various roles, including software architecture, design and development, network administration, and project management. Over his career, he has designed and helped to create systems for bio-medical manufacturing, agriculture, point of sale, credit card fraud tracking, general retail, construction, and healthcare.

Topics of Discussion:

[4:00] How an arcade game led Rocky to his career in software architecture, design, and development.

[5:05] What is CSLA, and what problems does it solve?

[8:40] Rocky defines business logic and what is not considered business logic.

[17:11] Rocky discusses his object-oriented approach, and inspiration from computer science Professor David West.

[19:25] A function library is where each rule is a function or a procedure.

[20:58] Rocky thinks that using object-oriented concepts is the way to go.

[23:51] Rocky’s preferred naming convention is to use a verb in the name.

[28:20] CSLA tries as much as possible to give you this home for business logic and then also provides some buffer between your business logic and everything from Windows Forms all the way up through Blazer.

[30:00] How does CSLA like to be used?

[31:00] The CSLA framework is geared around an architecture where you have, at the center, this business logic layer, and below that you have a data access layer, and above that, you have an interface control layer.

Mentioned in this Episode:

Architect Tips — New video podcast!

Azure DevOps

Clear Measure (Sponsor)

.NET DevOps for Azure: A Developer’s Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon!

Jeffrey Palermo’s YouTube

Jeffrey Palermo’s Twitter — Follow to stay informed about future events!

Programming with Palermo

programming@palermo.net

Rocky’s Blog

Rocky on Episode 33

Marimer LLC