Видео

Thank you so much for your note!

We completely agree with you on this one! When adopting a new technology it is always best to start with some small scale projects with well-defined scope. That way you can learn the practical lessons before you enlarge the footprint. Modernizing enterprise applications is always going to be a strategic initiative and it's essential to take the time and think it through properly. In this case, we do have a runway on these older .NET Framework applications measured in years. Unfortunately, we have also found that it sometimes does take years for enterprise organizations to go through this sort of transition. That's why we recommend that now is the time to start evaluating new technology alternatives and evolve a modernization approach before it becomes a crisis issue.

These are great questions and I'm so glad that you took the time to ask them. Over the years we have built systems using both relational and NoSQL database using many different approaches including EF. Most of the detailed answers to your questions are in the trellispark academy. I have summarized some of the key points for you below: We built a hybrid solution where we used the best bits of a NoSQL style document database on top of a relational database. That way we get the best of both worlds. The data is saved and managed as an XML document. A copy of the data is also made in a read-only relational lookup table and optimized for search. There is a minor performance impact on the record save, but the performance of the search more than makes up for it. The lookup tables can be a subset of all of the record fields and indexed for query and list operations. When displaying a selected record, we pull the entire XML record and then combine it with a form definition to produce the required user experience. The rendering process is split between the REST API that pulls the record, and the User experience building the page on the WASM client. The overall result is minimal transfer of data between the client and server to optimize network traffic. The UX rendering is WASM so that we can also fully leverage the client's resources. This makes for an extremely fast, secure and scalable user experience. Inside the REST API, all of the logic that usually sits inside your EF/CRUD code-behind, fields, states, roles, custom logic etc. is completely eliminated. It is baked into a single form builder that combines the record XML with the form data definition. That takes away 90-95% of the code that you would normally have to build and test. It means that modifying your form definitions to change your data model doesn't require any code changes, re-compilations, re-deployment or testing. The advantage of the XML storage format is that we also get row level security, versioning, bookmarking, auditing etc. essentially for free. Bottom line is that we can build out solutions that run at least as fast as an equivalent EF framework at a small fraction of the business cost and risk. The solutions run on a smaller infrastructure footprint and are easy to modify as business needs evolve delivering value to market faster.