Portal Architecture

After having identified and designed the basic needs of your portal, you can now begin to build the infrastructural requirements to support those designs.  Web applications will require a web server and potentially databases for ancillary data like ASP.NET security information. 

Mobile vs. Desktop vs. Browser Application

Things to consider when making a decision about your Dynamics 365 portal architecture:

  1. Consider users.  Who will be the majority of the users?  How will they be accessing Dynamics 365?  We are in a mobile driven world where most individuals between 12 to 70 years old own a mobile device. Of those mobile users 46% use a mobile application to help them with shopping and on-the-go research.
  2. Consider platform limitations. The desktop is limited by its hardware, and must meet the hardware requirements to run the application. Web applications can provide access to complex applications delivered from a centralized infrastructure. A Mobile device is limited by its screen area, available memory and data connection.
  3. Consider deployment. Desktop applications must be installed on a particular operating system and deployed for each PC. Web applications can have less deployment or update effort for hundreds or thousands of PCs.
  4. Consider security. Does your organization have information that requires additional security? What precautions need to be taken? Online and mobile banking options have become preferential due to convenience and flexibility they offer.
  5. Consider availability. Web applications are universally available but, rely on internet connectivity in order to work.  In comparison, a stand-alone desktop solution is not inhibited by connectivity. Something to consider with a mobile device is that the application could quit or restart when the user receives a call.
  6. Consider supported device. What is the preferred browser at your organization?  How does leveraging the same Web application on different browsers change the user experience?