Technology layers or Technology stacks You find it everywhere

There are several Technology Stacks we use and do not notice that they are exist. It is important to know that they are exist. Because some times you might start development at too much low level.

When what you need is rapid prototyping It is important to develop or choose a wanted technology solution for each step, I want a good one that will save time, and with "waste management" in mind (random notes).

• have it all done ahead.

To be able to do rapid prototyping you have to have all of the below implemented and chosen and have a boilerplate example for each.

** So be careful starting too low in the stack. It means that you will have to develop by yourself all the way up to the high level. **

Here I try to define what is there, what are all the parts of the system on each level.

GUI technology stack:

• ui functionality implemented - jquery plugins, ajax.org Ext iUI jQTouch
• low level operational javascript framework - sammy js
• low level javascript framework - jquery , zepto.js
• html tags markup style
• design
• css and css3 for mobile apps
• html

FRAME WORK technology stack:

• community for plugins
• plugins manager and app scaffolding generation program
• plugins for framework
• operational framework
• OOP and plugins system implementation
• low level framework like - router, database connection , integration connectors like ajax, and RPC
• libraries and native bindings
• programming language interrupter
• server

DATABASE technology stack:

• database - model - api /query language
• database - driver - api / query language
• database - command line - api / query language
• database - administration

INFRASTRUCTURE technology stack:

• servers dashboard
• distributed file system
• reverse proxy
• load balancing
• firewall management
• ssh access & user management
• logs scaling
• automatic server installation and configuration.
• automatic scaling
• Automatic deployment of VPS grids etc..

home