150 likes | 163 Views
Learn how to implement a website from concept to monetization, covering technical aspects like operating systems, service-specific software, and data management systems. Explore remote services, hardware, software, and network considerations.
E N D
IDK0040 Võrgurakendused IBuilding a site: Implementation Deniss Kumlander
From A to B • idea • money • content / users / services business/technical implementation splitter • operating system (e.g., Windows XP or Unix) • service-specific software • data management system (Database, files [flat] etc) • TCP/IP • Resources (processor, HDD, network)
Using services remotely • Remote server is administrated by somebody else (read controlled) • You just download your site • Different levels of services: • Just HTML • +PHP or ASP • +DB • +performance
Domain • www.ttu.ee/yourname or • www.yourname.eu / .com etc • Registrar + DNS address
Control PC, use (restricted) network • You do whatever you want on software, installs etc. • You must administrate your site and monitor avoiding downtime. • ISP provider defines what ports are open. • Dynamic IP address? • http://www.dyndns.com
Control PC, control network • + You can open/close/control ports, gateways, routers
Hardware • Computer (number of users, connections, materials, applications) • Personal • Server • Mirrored disks (RAID) • Router (firewall, gateway) • UPS
Software • Windows / UNIX • IIS / Apache • PHP / ASP • ORACLE / MS SQL Server / MySQL
Network • Network channel • Upload “Bandwidth is cheap and getting rapidly cheaper, notably because of cable modems. Don't make too many decisions based on the assumption that users will be connecting at 56K”http://philip.greenspun.com/panda/server • Download • Limits • Internal network
Conclusion • Decide what you are going to concentrate on • How you do that • What will you need
Development cycle steps • Build a data model • Define activities / functions to be used to produce, get, report etc these data • Defines forms you are going to use • Write program implementing those activities, i.e. mapping data to forms and parsing parms to get data Prototype using a simple (text only?) interface and thereafter implement a graphic UI if the simple one is accepted (move from simple to complex)
Data Storage • Restricted amount of data • Flat system (files based) • Sufficient amount of data • RDBMS
DB implementation • Connection-pooling • Cache (enough RAM) • ? Load balancing • Restrict connecting directly to DB computer • ODBC or direct string mapping Web browser/client Request Web server (IIS, Apache) Load & Run Program (PHP, ASP) Open connection Close DB (ORACLE, MySql, MS SQL Server)