.NET Technology Guide for Business Applications, by Cesar de la Torre and David Carmona!
Here’s a little bit about the guide:
1. Key takeaways
Select your architecture approaches and development technology based on your specific application’s priorities and requirements.
A single architecture and approach won’t work for every type of application. The Microsoft development stack and .NET are extremely flexible and offer many possibilities, but it’s essential that you choose specific approaches and technologies based on the kind of application—or even subsystem—you build. Each application will have very different priorities and tradeoffs that must be taken on different paths.
Business application modernization goes further than simply building mobile apps. Mobile applications must rely on and extend your foundational business applications.
To be successful, mobile apps must be built with deep integration into your current foundational business applications. Mobile business apps should be part of the larger enterprise ecosystem and substantially extend foundational business applications, whether the foundational systems are established legacy applications or new, large, mission-critical applications built with innovative, scalable, and elastic services, and since user experience is important in applications, and that’s why the use of UX Design services like תהליך אפיון is essential to make the apps more usable for the user.
Positioning your application or subsystem within a global patterns segmentation will help you to choose the right approaches and technologies.
It is fundamental to position your application/subsystem in the right segmentation area. The right approaches and technologies for each of the following application types could potentially be very different:
- Emerging application patterns
– Devices and services
- Established application patterns
– Small and medium-sized business applications
– Large, mission-critical business applications
2. Purpose of this guide
This guide will help you effectively select the right Microsoft development technologies and approaches for your .NET custom application development, depending on the priorities you have for your application and for your business domain.
This guidance does not cover Application Lifecycle Management (ALM) practices. For additional guidance on this topic, you can visit the Visual Studio ALM website at www.microsoft.com/visualstudio/alm.
Who should use this guide
This guide will be useful to decision makers, software architects, development leads, and developers who are involved in selecting the technologies to use for their applications and projects based on Microsoft development platforms.
Specifically, it covers custom enterprise application development, although ISVs might also find the information and recommendations useful.
This guide does not cover development solutions based on Microsoft business-market products, such as vertical solutions based on Dynamics CRM or Dynamics ERP.
How to use this guide
This guide covers a broad spectrum of software development options that focus on business applications. It is written as a reference document so that you can go directly to an area you’re interested in, such as Section 4, “Emerging application patterns,” or “Large, mission-critical business applications” within Section 5, “Established application patterns.”
We do recommend that you read Section 3, “Overview,” for context before you dive deeper into the individual sections.