Microsoft Dynamics GP Architectural Foundations Series - Conclusion

This is article 6 of 7 from the series Microsoft Dynamics GP Architectural Foundations Series - featuring Microsoft's Tim Brookins.

Tim's whitepaper was originally published in 1999 and it's reproduced here with his permission.









Conclusion

A typical architecture white paper will usually babble on about the popular technologies of the day like Client/Server, SQL Server, Thin Clients, Browser Clients, Stored Procedures, FRx, Office Integration, Report Writing, 2-Tier, 3-Tier, ODBC, Internet, Transact SQL, Windows NT, etc.

This document operates at a more strategic level, primarily because the endless list of technologies are changing constantly. In short, technologies come and go, but architectures are built for the long term. Any meaningful discussion of product architecture must be based on principals or philosophies that are technology independent.

The eEnterprise product architecture is based on a single fundamental premise, with four supporting philosophies:

The value of the business management system is contained in the Business Logic.

• The business logic must be Built to Last
• The business logic must be Built to Grow
• The business logic must be Built to Leverage
• The business logic must be Built to Fit

This document has been dedicated to describing these philosophies in detail. When a specific technology like C++ or VBA has been mentioned, it is only an example of how current technologies are being used to support these long-term philosophies.

While I've tried to avoid mentioning specific technologies in order to focus on the long-term architecture, keep in mind that eEnterprise is the industry leader in technology support. Client/Server, SQL Server, Thin Clients, Browser Clients, Stored Procedures, FRx, Office Integration, Report Writing, 2-Tier, 3-Tier, ODBC, Internet, Transact SQL, Windows NT... Yes, eEnterprise supports them all!

But in the end, never allow a laundry list of technologies from any vendor cloud your vision. Always keep in mind that today's "must have" technologies will quickly become tomorrow's "must replace" technologies. Great technology is not enough. Great functionality is not enough. You need a product that has an established track record of sustained technology and functionality leadership that only a superior architecture can deliver. I hope you'll agree the eEnterprise architecture has the solid foundations you can trust to take your business into the future.





In the next article Tim Brookins offers his insight.


Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

eConnect Integration Service for Microsoft Dynamics GP 2010