This part of the Project Life Cycle uses all the information garnered so far to decide on the best architectural solution for your project. We have no preferences only the best fit.

Considerations

Cost - We would all like the latest technology but that is not always financially possible. If it is possible - and most times it is - to use a cheaper solution and then easily upgrade to the most up to date at a later date then we do it.

Coding Languages - Sometimes old is better and sometimes new is. There are no hard and fast rules. Cobol for instance was a language many expected to be replaced by C/C++ but many financial houses found their current cobol systems worked well enough with cobol and did not replace for years until the web programming languages created an oppportunity to provide online accounts. If you want your site to be accessible to mobile users then html5 is essential but you need tbe aware that many smartphone memories are still lagging some way behind the performance of laptops / pcs and tablets.

Performance - Do you need a state of the art system capable of handling millions of transactions or will a few 1000 suffice? Why have the very best before you can use it to its capacity? Take a cheaper option and ensure you can upgrade quickly and efficiently when your business accelerates and grows.

Own Server - Do you need your own server or can you upgrade when the time is right and revenues increase? If the demand requires your own server can you set up virtual servers to pipe traffic to different virtual sites to maintain performance when multiple users use your site simultaneously.

Security - What level of hardware security is needed to keep data and users safe? These are costly additions so is it worth in the beginning sharing a server and the cost with other users?