Traditional E-Commerce Application
- Idea: We want to setup an ecommerce website where we sell electronics, mobile phones etc
- Initial Decisions:
- Start with existing opensource ecommerce and start selling asap
- Evaluate all possible infrastructures.
- Solutions:
- Find an ecommerce application which fits my purpose
- Team is tilted towards nopCommerce
- Find an ecommerce application which fits my purpose
Evaluating infrastructure
- Understand Application Architecture
- Made some os/software choices
- Possible Infrastructural choices
- Buy Servers and run it in our organization (On-premises)
- Try cloud
- Try SaaS (nopCommerce supported hosting)
- Managing Datacenters
- Networking
- Switching
- Routing
- Racks
- Servers
- Virtualization
- Networking
- From network perspective
- We have two servers
- web: should be accesible from internet
- db: should not be accessible from internet
- The above case poses a challenge in a on-premise environments as i need to design DMZs ( De militarized Zones)
- We have two servers
- Cloud in this case seems sensible as we can come up with Application, Quickly and securely as well
- Cloud offers Platforms as a Service (PaaS) where we get databases directly and configuring backups is one-click
-
To run website we have two options
- IaaS:
- We get ubuntu linux vm
- installing all necessary softwares
- maintaince (updates/patches) is our responsibility
- PaaS
- We get .net platform
- directly deploy nopCommerce
- IaaS:
-
Summarize:
- We prefer cloud
- For mysql database we need a PaaS
- For nopComemrce web application we got with IaaS (virtual machines)
-
IaaS vs PaaS vs SaaS
