Silverlight 4 Reference Architecture for LOB apps

•Als PPTX, PDF herunterladen•

2 gefällt mir•1,147 views

This document proposes a Silverlight 4 reference architecture for line-of-business applications that focuses on requirements like testability and the single responsibility principle. It compares using Entity Framework and WCF RIA Services versus a domain model with NHibernate and WCF Data Services, and recommends the latter approach combined with patterns like MVVM, commanding, and domain events. It provides background on relevant frameworks and patterns and contact information for the author.

Technologie

A Silverlight 4 Reference Architecturefor Line-of-Business Applications Dennis Doomen dennis.doomen@avivasolutions.nl

Dennis Doomen Requirements ,[object Object]

…whateveryour project requires,[object Object]

No eagerloadingViews (XAML + C#) Shell View Models Silverlight 4 Application Controller Service Agent DTOs Service Interface WCF Workflows Domain Model Service Actions NHibernate(+ Fluent & LINQ) Service Agents Unit-of-Work Repositories Database Backoffice System External Service

Dennis Doomen Model View-ViewModel INotifyPropertyChanged Events XAML (+C#) ViewModel ServiceAgent {Binding} Command Call Model Loads

Weitere ähnliche Inhalte

Andere mochten auch

Introducing the silverlight cookbook

Dennis Doomen

During my last few talks I was surprised to learn how few developers are aware of the power of Microsoft OneNote, one of the products in the Microsoft Office suite. OneNote is an advanced digital notebook that I use for accessing my personal notes through SkyDrive or Office 365, as well as a shared notebook that agile teams use for keeping track of who is doing what. In fact, those who practice Test Driven Development will be surprised how essential OneNote is. In addition to OneNote, many other tools and add-ons exist that can really boost your productivity. Some you may know, some you don't. But do you already get the most out of tools like NuGet, GhostDoc, ReSharper, Notepad++, and many others? If you're in doubt, come check out my session. I'lI show you what I use to be as efficient as possible in my job as a professional developer.

Little productivity tools every developer should use

Dennis Doomen

Chalk and Talk: Silverlight, WCF RIA Services, Architectuur

Dennis Doomen

Breaking down monolothic systems into smaller components that are maintained by specific people in separate git repositories and distributed as NuGet packages is becoming the standard these days. But what if your component needs to expose some kind of HTTP end-point such as a WebAPI controller or an embedded management website? How do you host such a component in another system without affecting it's hosting model? This is were the Open Web Interface for .NET comes to the rescue. Even the next version of ASP.NET is completely based on OWIN hosting. In this session I'm going to explain you how to build OWIN middleware components and how to host these in an IIS website, a Windows Service or even in a command-line tool.

Building autonomous components with OWIN, PSake, NuGet, GitVersion and Swagger

Dennis Doomen

It's 2016, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven't really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks. And even if you believe you are well versed in the testing realm, join me anyway. Maybe we can learn some tips & tricks from the audience as well. Looking forward to it!

How to practice TDD without shooting yourself in the foot

Dennis Doomen

By now, I hardly think anybody needs an introduction to Git. It's becoming the de-facto standard for open-source projects, as well as the main source control system for a lot of corporations. However, Git is just one part of it. Combining it with modern hosting platforms like Github, Bitbucket or Visual Studio Online allows some truly fascinating ways of working with lots of people. Pull Requests, GitFlow, MyGet and GitVersion are crucial in a scalable software development organization. In this session I'll share how we've been using Git and these tools for over two years now. I'll explain how these tools helped us. I'll show you some awesome uses of Git that will truly help you in your day-to-day work.

Git like a Pro (How to use it as it was meant to)

Dennis Doomen

I've recently got the opportunity to work on a large enterprise-class system that needs to be deployed on multiple occasionally connected oil platforms and boats. Already the system's architecture was based on the Command Query Separation principles, this gave us a completely new challenge. After several months of looking at alternatives, we decided to go the Event Sourcing direction. In this in-depth session, I'd like you to learn the many alternatives we observed, the pros and cons, and the technical details of our final solution in which we use EventStore 3.0 and elements of NCQRS and Lokad.CQRS to synchronize systems over unreliable connections in a very efficient way.

Building occasionally connected applications using event sourcing

Dennis Doomen

Andere mochten auch (7)

Introducing the silverlight cookbook

Little productivity tools every developer should use

Chalk and Talk: Silverlight, WCF RIA Services, Architectuur

Building autonomous components with OWIN, PSake, NuGet, GitVersion and Swagger

How to practice TDD without shooting yourself in the foot

Git like a Pro (How to use it as it was meant to)

Building occasionally connected applications using event sourcing

Ähnlich wie Silverlight 4 Reference Architecture for LOB apps

Most of us will be familiar with the standard 3- or 4-layer architecture you often see in larger enterprise systems. Some are already practicing Domain Driven Design and work together with the business to clarify the domain concepts. Perhaps you’ve noticed that is difficult to get the intention of the 'verbs' from that domain into this standard architecture. If performance is an important requirement as well, then you might have discovered that an Object-Relational Mapper and a relational database are not always the best solution. One of the main reasons for this is the fact that the interests of a consistent domain that takes into account the many business rules, and those of data reporting and presentation are conflicting. That’s why Betrand Meyer introduced the Command Query Separation principle. An architecture based on this principle combined with the Event Sourcing concept provides the ideal architecture for building high-performance systems designed using DDD. Well-known bloggers like Udi Dahan and Greg Young have already spent quite a lot of of posts on this, and this year’s Developer Days had some coverage as well. But how do you build such a system with the. NET framework? Is it really as complex as some claim, or is just different work?

CQRS and Event Sourcing, An Alternative Architecture for DDD

Dennis Doomen

Dynamics 365 Saturday - London 2018 - New Features and Deprecations with Dyna...

Ramon Tebar

Shaping serverless architecture with domain driven design patterns

Shimon Tolts

Shaping serverless architecture with domain driven design patterns

Asher Sterkin

Introduction to WCF RIA Services for Silverlight 4 Developers

Saltmarch Media

Cloud Computing basic

Himanshu Pareek

January 2017 - Deep dive on AWS Lambda and DevOps

David McDaniel

TechInsight - Real World Implementation of VDI

Lai Yoong Seng

Kent Mitchell, Director of Product Marketing at Zend, led this session at the RightScale User Conference 2010 in Santa Clara. Session Abstract: The cloud is the new “holy grail” for a lot of people. The cloud enables sites to ramp up new servers for increased load and then ramp down servers when the load decreases. This minimizes upfront costs and provides “pay as you go” cost structure. This scenario is very compelling, especially for startups where budgets are tight. But it also presents some challenges such as making sure the new servers are identical to the existing servers, monitoring the ever-changing cluster, and retaining critical problem data when servers ramp down. In this session, we’ll demonstrate how using Zend Server Cluster Manager together with the RightScale Cloud Management Platform provide solutions for managing cloud-based, highly available PHP server clusters.

High Availability PHP Clusters in the Cloud

RightScale

Opalis - Infrastructure Optimization for the Future

Dave Kawula

Keynote Dev Tech Days09

Gregory Renard

Mike Taulty MIX10 Silverlight Frameworks and Patterns

ukdpe

Basics of Silverlight 1

Meenakshi Kumar

Decoupling Drupal - Drupal Camp Toronto 2014

Alex De Winne

MAX 2008: Build collaborative applications with Flex LCDS and Cairngorm

Xavier Agnetti

.NET Cloud-Native Bootcamp- Los Angeles

VMware Tanzu

Accessing sap and_mainframe_data_and_applications_via_share_point

Yuval Birenboum

"Is serverless another passing technology fad or the new standard for application deployment in cloud computing?” It’s a good question and the topic of this presentation. We will discuss the current state of serverless computing and the many considerations before investing time and resources in serverless infrastructure. For many, data center priorities have shifted from absolute uptime and performance to ”move fast and break things” as espoused by Silicon Valley, a great mantra for those with limited legacy systems and a greenfield of new products. Though the question for many enterprises though is "How does serverless integrate into their existing data center strategy?" The discussion will not only explain the state of today’s growing serverless landscape but how you can integrate your existing data center with a cloud-native serverless architecture.

Serverless 2019 and Beyond

Mark Hinkle

Building Enterprise Interoperability Applications Using Microsoft

webhostingguy

Building, testing, and deploying AWS Lambda-based, serverless applications introduces new challenges to developers whose development workflows are optimized for traditional VM-based applications. In this webinar, we will introduce one method for automating the deployment of serverless applications running on AWS Lambda. We will first cover how you can model and express serverless applications using the open source AWS Serverless Application Model (AWS SAM). Then, we will discuss how you can use CI/CD tooling from AWS CodePipeline and AWS CodeBuild to build an automated development workflow for your serverless app. Learning Objectives: 1. Understand the fundamentals of the microservices architectural approach 2. Learn best practices for designing microservices on AWS 3. Learn the basics of Amazon EC2 Container Service, Amazon API Gateway, AWS Lambda, and AWS X-Ray"

Building a Development Workflow for Serverless Applications - March 2017 AWS ...

Amazon Web Services

Ähnlich wie Silverlight 4 Reference Architecture for LOB apps (20)

CQRS and Event Sourcing, An Alternative Architecture for DDD

Dynamics 365 Saturday - London 2018 - New Features and Deprecations with Dyna...

Shaping serverless architecture with domain driven design patterns

Introduction to WCF RIA Services for Silverlight 4 Developers

Cloud Computing basic

January 2017 - Deep dive on AWS Lambda and DevOps

TechInsight - Real World Implementation of VDI

High Availability PHP Clusters in the Cloud

Opalis - Infrastructure Optimization for the Future

Keynote Dev Tech Days09

Mike Taulty MIX10 Silverlight Frameworks and Patterns

Basics of Silverlight 1

Decoupling Drupal - Drupal Camp Toronto 2014

MAX 2008: Build collaborative applications with Flex LCDS and Cairngorm

.NET Cloud-Native Bootcamp- Los Angeles

Accessing sap and_mainframe_data_and_applications_via_share_point

Serverless 2019 and Beyond

Building Enterprise Interoperability Applications Using Microsoft

Building a Development Workflow for Serverless Applications - March 2017 AWS ...

Mehr von Dennis Doomen

I'm sure every developer wants to be able to change code with confidence and without fear. Readable and self-explanatory code is one aspect of that. Too much coupling is another major source of problems that prevent you from changing one part of the system without causing side-effects. In this talk, I'd like you to show you common sources of unnecessary coupling and offer you options to help prevent and/or break those. I'll talk about how principles like Don't Repeat Yourself and Dependency Injection can be a double-edge sword, how to detect too unnecessary dependencies and how to use the Dependency Inversion Principle to unravel some of those. And yes, I will also talk about controlling dependencies on the package level. Challenge 1. How to prevent too much coupling? 2. We are tought to decrease coupling and increase cohesion 3. How do you increase cohesion? By applying DRY! 4. But DRY creates more coupling 5. And too much decoupling results in a forest of abstractions 6. The solution is… find a balance (or "it depends") On the architecture level 1. Use architecture style that embraces DIP (e.g. Onion, Hexagon, Clean Architecture) 2. Organize your code along functional boundaries -> this will make it easier to break off that boundary for rebuilding/strangler/microservices. 3. Apply DRY within those boundaries only, but allow shared services for complicated capabilities 4. Align your test scope with those internal boundaries… On the package level • Classes and interfaces that are almost always used together should be packaged together. Those that don’t meet that criteria don’t have a place in that package • Packages should not require changes (and thus a new release) for unrelated changes. • There must be no cycles in the dependency structure • A package should only depend upon packages that are more stable than it is or abstract packages On the code level • Avoid technical folders and organize them by functionalities or capabilities • Things in adjacent folders usually mean they are separate boundaries • Use the Tell, Don't Ask principle • Use the Law of Demeter to detect unnecessary coupling • Encapsulate primitive types and collections in specific types • Dependency injection is great, but try to avoid a global container • It's fine to inject concrete classes inside boundaries Strategy for legacy code 1. Ensure you have a safety net using characterisation tests 2. Find existing seams and decouple them better a. Identify modules or functional slices b. Identify groups of classes that are supposed to be used together and are designed to be reusable c. Identify interfaces or abstractions in DI registration code and see if they are truly designed for reusability d. Assume that code in adjacent folders is supposed to be independent e. Move code from different technical folders that belong together in their own (functionally named) folderPublic 3. Use that to define (and visualize) the target architecture

Getting a grip on your code dependencies (2023-10)

Dennis Doomen

We all love to build greenfield projects, but the reality is that in most jobs you have to deal with a lot of legacy code. This doesn't mean the code is bad. It just means that choices were made that were the right ones at that time, or that the developers were not entire up-to-date with modern development practices. And that's exactly what this talk is about. I enjoy taking such a codebase and gradually introduce architectural seems, add a proper build pipeline, introduce temporary tests and then gradually refactor the codebase to combine more maintainable, testable and reliable. So in this talk, I'd like to unfold my extensive toolbox of practices, principles, tools and mindset to help you improve your legacy code without jeopardizing your business. Understand production environment See which vinaries are running in production and what config files are used Verify the code and the production release are in sync, e.g. DotPeek Analyze logs to understand what features are used Try to get it to run on a local environment Understand code Generate project diagrams and class hierarchies Find origin calls and destination of a parameter using Rider Use navigation options to find inheritors, usages, etc. Use the namespaces and project names to understand the relation Have Rider's AI Assistant or ChatGPT explain the code Track all documentation in a single place Build C4 diagrams Find dead code Reduce the scope of types and members to internal to find more dead code Detect code inefficiencies and dead code using Rider Remove commented out code Build a safety net If therea are tests, add code coverage reporting using Coverlet and use that to find dark spots (HTTP API) Characteristics tests using FluentAssertions, Bogus, xUnit. Use AI to generate them. It's fine, you'll delete them later on Use test containers for .net t lo include the databse Build a couple of end to end UI tests e.g. using Cypress, Playwright, efc Improve deployability Add scripts or builds steps to run the code locally, Nuke build pipeline to get consistency Adopt a version strategy and name branches accordingly Adopt automatic versioning using GitVersion Adopt logging and exception strategy, e.g. Serilog Pulumi to automate PR deployments Improve code Treat all warnings as errors and fix thhem Editorconfig / eslint so auto-format works Configure a personal Rider/R# clean-up profile to auto-format file, project and solution Roslyn analyzers Microsoft.CodeAnalysis.BannedApiAnalyzers StyleCop.Analyzers CSharpGuidelinesAnalyzer Roslynator.Analyzers Meziantou.Analyzer Enable nullable types per file Move new code to .NET 6+ or cross-compile Switch to newer C# versions, possibly using Polysharp File-scope namespaces Target-typed news switch expression String interpolation instead of string.format Use Directory.Build.Props to reduce duplication Improve naming whenever you can Encapsulate prim itive types and collections in d

Tools and practices to help you deal with legacy code

Dennis Doomen

Providing a high quality library like that doesn't come for free. We've been trying to write code that is clean enough for our contributors, write tests that are self-explanatory, ensure breaking changes are strictly controlled and try to make it easy to use. In this talk, I'd like to share the tools and techniques we have been using. I'll talk about the release strategy, documentation, versioning, naming conventions, code structure, the build pipeline, automated testing, code coverage, API change detection, multi-targeting and more. In this talk, I'd like to share the tools and techniques we have been using, how they've enriched our day jobs, and how they may do that for you too. I'll talk about the release strategy, documentation, versioning, naming conventions, code structure, the build pipeline, automated testing, code coverage, API change detection, multi-targeting and more.

What you can learn from an open-source project with 250 million downloads

Dennis Doomen

Getting a grip on your code dependencies

Dennis Doomen

About 15 years ago, I got inspired by a series of posts on Test Driven Development written by the Jeremy D. Miller. Now, with many years of great and not-so-great experiences practicing Test Driven Development, I thought it is the time to capture my own “laws”. The term "law" is obviously an exaggeration and "principles or heuristics" cover my intend much better. Either way, I want to talk about the scope of testing, using the observable behavior, naming conventions, state-based vs interaction-based testing, the impact of DRY, patterns to build useful test objects and some of the libraries and tools I use. In short, everything I try to follow every day I write, review or maintain code.

My Laws of Test Driven Development (2023)

Dennis Doomen

Event Sourcing is becoming more mainstream these days, and a lot of conferences have demonstrated the pros and cons of this architecture style from multiple angles. I've done a few of these and publishes a lot of articles on best practices and solutions to common problems. But what nobody did was to show you how to build an event sourced systems in the .NET ecosystem. There are a lot of open-source projects that you can use, so you'll need to find a right mix and your own code to that. So let me show you how I would implement this in .NET with almost 10 years of Event Sourcing experience behind my belt.

Design patterns for Event Sourcing in .NET

Dennis Doomen

Who remembers the days were you had to manually setup a physical server somewhere in a 19 inch rack? Nowadays those physical racks have been replaced by virtual machines provided by Google, Microsoft and Amazon. But some people are still provisioning them manually. The more mature organizations will script most of the provisioning using the native CLI or HTTP API provided by the specific cloud platform, but quite often those are maintained separately from the code of the system that is being deployed. Terraform by Hashicorp is another attempt to support infrastructure-as-code by using a declarative syntex to define the desired infrastructure. But then again, Yaml isn't really suited for anything but simple single-file configuration settings. Yaml isn't code and doesn't provide real Intellisense, line-by-line debugging and most importantly, refactoring. But what if you could use C# and .NET to provision your infrastructure and treat that code as first-class citizens of your codebase, including all the capabilities that you would expect? Well, let me show you how Pulumi for .NET will allow you to evolve your infrastructure code with the rest of the code base without turning it in a big spaghetti of Yaml files.

Automate Infrastructure with Pulumi and C#

Dennis Doomen

Whether you're just writing your first unit test or have been practicing Test Driven Development for many years, I'm sure your biggest challenge is to find the right scope for testing. Unfortunately a lot of books and guidance seem to imply that every class or type should be tested separately. Well, I can tell you from 15 years of unit testing experience that that's the best way to shoot yourself in the foot. In this session, I'm going to show you some concrete examples and why I chose a certain boundary for the "unit" in unit testing. I will also share design heuristics I use myself to find those boundaries and why those are not guidelines. I'll also illustrate how principals like DRY and SOLID can be both a blessing and a curse that may lead to the wrong design choices

What is the right unit in unit testing (UpdateConf 2022)

Dennis Doomen

I don't have to tell anybody how awesome Event Sourcing is as an architecture style. But those that have been using it in production must have experienced the pains of keeping the upgrades fast enough, especially if you use a more traditional relational database like SQL Server. I've once heard somebody say: "If it's slow, make it faster", but rebuilding a big projection is simply a very expensive operations and involves a lot of network traffic between the application and the database servers. Over the years since we adopted Event Sourcing, we've been experimenting a lot and have implemented various improvements to make those reprojections faster. And we haven't stopped. We're already working on some new ideas lately. So in this session, I'd like to share those techiques, their pros and cons and how we implemented them on a more detailed level.

Slow Event Sourcing (re)projections - Just make them faster!

Dennis Doomen

Enough books have been written, articles have been published and Youtube videos have been posted about how you should be behaving as a software developer, Scrum Master or team lead. To be original in this unoriginal world, I started thinking about the things you should NOT be doing. I came up with 50 tools, practices and principles covering topics like dealing with complexity, productivity, architecture, testability, traceability, maintainability, transparency and predictability that I believe hamper you as a professional. That sounds like a lot, but I promise you a fun and entertaining session that I'm sure will trigger a lot of recognition.

50 things software teams should not do.pptx

Dennis Doomen

What is the right "unit" in unit testing and why it is not a class?

Dennis Doomen

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I'd like to share my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

A lab around the principles and practices for writing maintainable code

Dennis Doomen

It’s 2021, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, Dennis regularly talks to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session Dennis likes to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks.

How to Practice TDD Without Shooting Yourself in the Foot

Dennis Doomen

If I have to name a single biggest hype in software architecture land then it would be "microservice". They are supposed to be small and focused, can be deployed independently, can work with any technology and will solve all your monolithical problems. But we all know that silver bullets don't exist, plus technology should never be a goal, but merely a means to an end. Nonetheless, following the path towards real microservices is a great strategy for decomposing a monolith without the deployment complexity of the first. So how do you do that? What technologies does the .NET realm offer for us? In this talk, I'll show you some of the pros and cons of micro-services and its ingredients to leverage modern-day .NET and Event Sourcing to move your monolith into a bright new future.

Decomposing the Monolith using modern-day .NET and a touch of microservices

Dennis Doomen

Over the years I've spoken many times about what Event Sourcing is and shared many of the good, the bad and the ugly parts of it in blog posts and various talks. However, I've never talked about how to actually build a system based on this architecture style. I keep getting the same questions over and over again. Like when to apply Event Sourcing and at what architectural level. How to deal with transactional boundaries within and outside the domain. How to build projections that are autonomous, reliable and self-supporting. How to deal with upgrades and blue-green deployments. But also on how to handle bugs, design mistakes and crashing projections. Having made a lot of these mistakes myself over these years, it's time to share my current thoughts and opinions about this. Since the .NET space has a pretty rich set of open-source projections to support this, the examples and code will be .NET. But the concepts are universal, so don't let that scare you off.

Event Sourcing from the Trenches (DDD Europe 2020)

Dennis Doomen

After several in-depth talks about Event Sourcing, I realized that there's a large group of developers that may have heard about Domain-Driven Design, Command-Query Responsibility Segregation and Event Sourcing, but have not really connected the dots yet. So in this talk, I'd like to take a practical example of a simple domain and gradually introduce functional requirements to see how the principles behind DDD affect the way your entities are going to protect the business rules. After that, I'll introduce some real-world non-functional requirements and see if and how Event Sourcing and/or CQRS may or may not help to accomplish those.

Practical introduction to DDD, CQRS and Event Sourcing

Dennis Doomen

It’s 2019, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks. And even if you believe you are well versed in the testing realm, join me anyway. Maybe we can learn some tips & tricks from the audience as well. Looking forward to it!

How to practice TDD without shooting yourself in the foot

Dennis Doomen

A micro-service architecture is a great strategy for decomposing a monolith. In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future. If I have to name a single hype in software architecture land then I would have to mention the micro-service architecture. Micro-services are supposed to be small, have a very focused purpose, can be deployed independently, are completely self-supporting and loosely coupled. Ideally, micro-services are technology agnostic, but hey, we’re in the .NET space, aren’t we? And they are not a goal, but a means to an end. In fact, a micro-service architecture has many benefits and are a great strategy for decomposing a monolith. So how do you build a micro-service? What technologies does the .NET realm offer for us? And what if you don’t want to deploy them independently? In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future.

Decomposing the Monolith (Riga Dev Days 2019)

Dennis Doomen

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I like to share you my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

A lab around the principles and practices for writing maintainable code (2019)

Dennis Doomen

I recently was asked what I would do differently if I had the experience I have now. This got me thinking about the mistakes I've made, the traps I fell for and the dogmatism I became part of over the last 22 years of professional software developer in the Microsoft realm. In this talk, I'll be going down memory lane with you and share everything I've learned on architecture, tools, technologies, agile software development, maintainable code, automated testing, documentation and anything else that I think you should know. Prepare yourself for an event of stories, both good and bad.

Lessons learned from two decades of professional software development

Dennis Doomen

Mehr von Dennis Doomen (20)

Getting a grip on your code dependencies (2023-10)

Tools and practices to help you deal with legacy code

What you can learn from an open-source project with 250 million downloads

Getting a grip on your code dependencies

My Laws of Test Driven Development (2023)

Design patterns for Event Sourcing in .NET

Automate Infrastructure with Pulumi and C#

What is the right unit in unit testing (UpdateConf 2022)

Slow Event Sourcing (re)projections - Just make them faster!

50 things software teams should not do.pptx

What is the right "unit" in unit testing and why it is not a class?

A lab around the principles and practices for writing maintainable code

How to Practice TDD Without Shooting Yourself in the Foot

Decomposing the Monolith using modern-day .NET and a touch of microservices

Event Sourcing from the Trenches (DDD Europe 2020)

Practical introduction to DDD, CQRS and Event Sourcing

How to practice TDD without shooting yourself in the foot

Decomposing the Monolith (Riga Dev Days 2019)

A lab around the principles and practices for writing maintainable code (2019)

Lessons learned from two decades of professional software development

Kürzlich hochgeladen

MINDCTI Revenue Release Quarter One 2024

MIND CTI

Top 10 Most Downloaded Games on Play Store in 2024

SynarionITSolutions

Webinar Recording: https://www.panagenda.com/webinars/why-teams-call-analytics-is-critical-to-your-entire-business Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Why Teams call analytics are critical to your entire business

panagenda

Partners Life - Insurer Innovation Award 2024

The Digital Insurer

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...

Neo4j

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Abhishek Deb(1), Mr Abdul Kalam(2) M. Des (UX) , School of Design, DIT University , Dehradun. This paper explores the future potential of AI-enabled smartphone processors, aiming to investigate the advancements, capabilities, and implications of integrating artificial intelligence (AI) into smartphone technology. The research study goals consist of evaluating the development of AI in mobile phone processors, analyzing the existing state as well as abilities of AI-enabled cpus determining future patterns as well as chances together with reviewing obstacles as well as factors to consider for more growth.

Exploring the Future Potential of AI-Enabled Smartphone Processors

debabhi2

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

sammart93

Boost Fertility New Invention Ups Success Rates.pdf

sudhanshuwaghmare1

Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

With more memory available, system performance of three Dell devices increased, which can translate to a better user experience Conclusion When your system has plenty of RAM to meet your needs, you can efficiently access the applications and data you need to finish projects and to-do lists without sacrificing time and focus. Our test results show that with more memory available, three Dell PCs delivered better performance and took less time to complete the Procyon Office Productivity benchmark. These advantages translate to users being able to complete workflows more quickly and multitask more easily. Whether you need the mobility of the Latitude 5440, the creative capabilities of the Precision 3470, or the high performance of the OptiPlex Tower Plus 7010, configuring your system with more RAM can help keep processes running smoothly, enabling you to do more without compromising performance.

Boost PC performance: How more available memory can improve productivity

Principled Technologies

Building Digital Trust in a Digital Economy Veronica Tan, Director - Cyber Security Agency of Singapore Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

apidays

Scaling API-first – The story of a global engineering organization

Radu Cotescu

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

Tata AIG General Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

This presentation explores the impact of HTML injection attacks on web applications, detailing how attackers exploit vulnerabilities to inject malicious code into web pages. Learn about the potential consequences of such attacks and discover effective mitigation strategies to protect your web applications from HTML injection vulnerabilities. for more information visit https://bostoninstituteofanalytics.org/category/cyber-security-ethical-hacking/

HTML Injection Attacks: Impact and Mitigation Strategies

Boston Institute of Analytics

Kürzlich hochgeladen (20)

MINDCTI Revenue Release Quarter One 2024

Top 10 Most Downloaded Games on Play Store in 2024

Why Teams call analytics are critical to your entire business

Partners Life - Insurer Innovation Award 2024

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...

How to Troubleshoot Apps for the Modern Connected Worker

Exploring the Future Potential of AI-Enabled Smartphone Processors

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Boost Fertility New Invention Ups Success Rates.pdf

Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024

Boost PC performance: How more available memory can improve productivity

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

Scaling API-first – The story of a global engineering organization

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Data Cloud, More than a CDP by Matt Robison

Tata AIG General Insurance Company - Insurer Innovation Award 2024

A Domino Admins Adventures (Engage 2024)

HTML Injection Attacks: Impact and Mitigation Strategies

Silverlight 4 Reference Architecture for LOB apps

1. A Silverlight 4 Reference Architecturefor Line-of-Business Applications Dennis Doomen dennis.doomen@avivasolutions.nl

3. Pragmatic

4. Single ResponsibilityPrinciple

5. DependencyInjection

6. Don’t DIY

9. Rich domain models

10. Manyframeworks

11. Very flexibele

12. Lots of work

13. Lots of plumbingneeded

14. Notusing RIA frameworks

15. DTO conversiontroubles

16. No eagerloadingViews (XAML + C#) Shell View Models Silverlight 4 Application Controller Service Agent DTOs Service Interface WCF Workflows Domain Model Service Actions NHibernate(+ Fluent & LINQ) Service Agents Unit-of-Work Repositories Database Backoffice System External Service

17. Dennis Doomen Model View-ViewModel INotifyPropertyChanged Events XAML (+C#) ViewModel ServiceAgent {Binding} Command Call Model Loads

18. As Microsoft wants it…

19.

20. Simple domain models

21. Lessplumbingneeded

22. No DTO conversionsneeded

23. Maximizes RIA frameworks

24. Great for CRUD

25. Batching

26. CRUD-based

27. Domain model notpossible

28. No dynamicrelationshiploading

29. No enum supportViews (XAML + C#) Shell View Models Silverlight 4 Application Controller Domain Context Changesets WCF RIA Services Domain Service Business Actions Entities Service Agents Entity Framework Database Backoffice System External Service

30. Entity Framework and WCF RIA Services?

31.

32. Automatic change-tracking

33. Client-side LINQ

34. Code Sharing

35. Great for CRUD i.c.m. Entity Framework

36. Built-in authorization

37. OData support

38. WCF based

39. No rich domain models

40. No eagerloading

41. No enum support

42.

43. Code Sharing

44. Fluent interface

45. POCO support

46. Great integrationwith WCF RIA/Data

47. Mappingattributes

48. Mappingattributes

49. No free support forothervendors

50. No enum support

51.

52. Views (XAML + C#) Shell View Models Coroutines Caliburn Micro Unity 2 or MEF Silverlight 4 Application Controller Service Agent Bootstrapper DTOs Commands Enterprise Library 5 WCF Data Services Rest Service Command Service Command Handlers Domain Model Service Actions Policy Injection Logging Unity 2 of MEF Workflows Event Handlers Domain Events NHibernate(+ Fluent & LINQ) Service Agents Unit of Work Repositories Database Backoffice System External Service

53.

54. Automatic change-tracking

55. Great forquerying

56. OData support

57. Eagerloading

58. Projections

59. WCF based

60. Built-in authorization

61. Code Sharing

62. Client-side Validation

63.

64. Domain Events

65. Background InformationMVVM, Coroutines, Commanding, Querying, Domain Events, TestableRepositoryPattern Example Code, FrameworksThe CQRS Kitchen, CaliburnMicro, MEF, Unity 2, NHibernate, FluentNHibernate, FluentAssertions

66. Emaildennis.doomen@avivasolutions.nl Twitter @ddoomen Blogwww.dennisdoomen.net

Hinweis der Redaktion

MVVM

Silverlight 4 Reference Architecture for LOB apps

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (7)

Ähnlich wie Silverlight 4 Reference Architecture for LOB apps

Ähnlich wie Silverlight 4 Reference Architecture for LOB apps (20)

Mehr von Dennis Doomen

Mehr von Dennis Doomen (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Silverlight 4 Reference Architecture for LOB apps

Hinweis der Redaktion