Nebraska.Code() Sessions tagged architecture

Should I make the Transition to ASP.NET MVC Core? Will it Hurt?

In the past few years we have been exposed to great change in the Microsoft technology stack. With the release of ASP.NET Core it is often a common question from developers as to when/how/should existing products be converted to core. This expands to more questions such as: Can I upgrade in place? Will this disrupt my development cycle? Is today the right time to do so? Should I wait? Do I have to re-write? All amazing questions

This session will review the differences between the full platform & the core platform, as well as the justification & decision process as to which solution is the best for your organization. The session will end with tips & recommendations for the best method to transition and convert to the new framework.

Speaker

Mitchel Sellers

Mitchel Sellers

CEO, IowaComputerGurus, Inc.

Android Architecture using Reactive MVVM

Last year Android came out with a few libraries to help you architect your application and documentation of recommendations to implement a good architecture. I will discuss LiveData, Room, ViewModel, and how to use those to create a reactive MVVM app. I will also show code that I wrote demonstrating how to use all of these patterns.

Attendees will learn what reactive MVVM is, how to use Android Architecture components to create a MVVM app, and leave with an example GitHub repository that is an example of everything that is talked about in the presentation.

Speaker

David Corrado

David Corrado

Mobile Application Developer, Werner / Corrado Developers

Domain Modeling - Many Models are Simpler Than One

Have you experienced the pain of having a large database table with many columns to handle storing complex entities? Have you experienced the pain of having a large function or class so complex you won't touch it for fear of what will break?

It's common to try to use one model of of the elements of your domain to try to serve all functionality required. The truth, though, is that not all needs require the same model. Different parts of your problem look at the same elements in different ways. A customer is a credit card to your billing department and a mailing address to your shipping departement. They look at things differently and should use different models.

One of the main lessons of Domain-Driven Design is that a domain can be decomposed into bounded contexts where smaller pieces of the problem can be modeled and addressed. Learn about the ways you can use multiple models to build an model that is simpler and more useful.

Speaker