|Number of votes:||0|
"If Your Business Isn't Evolving, It's Dying". Along with the businesses, EPiServer is also evolving. In result of a new big merger a new brand names is already in market, “EPiServer Digital Experience” (EDE). Growing E-Commerce websites are focusing on customer experience and doing a lot to engage their customers. EPiServer Digital Experience is a response to evolving business to meet the requirements of the time.
I am taking this opportunity to review what different modern content management / commerce systems are offering. Are we using up to date technologies and methodologies in our offices to meet the challenge of evolution?
I am studying a hypothetical case (Credits: Allan Thran). Hotel Finder Project
Business Name is Epi Tours (does not exist), they are tour operators and want different websites for user whom are not their direct clients but they are looking for hotels across the globe.
Generally, websites are designed with consideration of the user, the system (the IT infrastructure), and the business goals. For each of these areas we outline key scenarios and identify important quality attributes (for example, reliability or scalability) and key areas of satisfaction and dissatisfaction.
Here is a short summary of ET’s business goals.
Based on above business requirements, there are following high level concerns that we need to deal with in this project while architecting the application
Generally speaking, A solid foundation is important for any software so for a website too and for that we architect our application. A well designed system avoids failures and instability, it has been learnt from the history of software failures. Architecture consists of significant decisions, structural elements, interfaces and behaviours to interact with those elements. Other aspects that come in consideration of a solution architect are as following. Functional requirements (what the business do, bookings, orders, promotions etc.), Operational requirements (How business does functions as monitoring, controlling, resources consumptions etc.), Technical requirements (Computer interaction of Operations, Technology requirements, Inventory recording, applying promotions, introducing new trends), Performance, Security, Manageability, Maintainability, Usability, Adaptive, Flexibility, Reusability, Comprehensibility, Trade-offs and Aesthetic concerns (readers are welcome to add these concerns in comments)
To achieve these business goals rather to build everything from scratch, I will get the advantage of market maturity principal and will investigate existing CMS/Commerce/Search/Merchandise/Digital Marketing/UI/Hosting systems/options and will work on some flexible design for rest of the business requirements. For selecting appropriate technologies I will consider application type, deployment strategy, quality attributes, and cross cutting concerns of business as discussed above.
We have a wide range of products available in market. Every product has its own benefits and drawbacks too and is nearly ready to meet the evolving challenges. As a solution architect we need to look what the business needs and then compare those to budget and how worthy those are for business. For Commerce, CMS, Search, Merchandising and digital marketing requirements strong candidates are Hybris, SiteCore , EPiServer and Magento with Drupal/Word press.
I am ignoring Demand ware, they will own you as soon as you start work with them. Sitefinity, out of the box E-Commerce capabilities are very limited. Umbraco, not enough to support complexity of the project.