While interacting with many learners, I realized that not many learners were aware of the real product software building. I am surprised and shocked to know that many learners were not even aware of the source code management. As mentioned earlier, I realized that not many software trainers are acquainted with the life cycle - they all seem to talk about the general stuff such water fall model and scrum.
So, I have written down the tutorial which would give you a walk through of building a software.
There are various kinds of Applications:
* Client: * Yes
* Server: * Yes
* Client: * Yes (Major Work)
* Server: * Yes(mainly for showing leaderboard etc)
* Client: * Mainly in HTML, CSS & Javascript
* Server: * Yes, heavily server (Java/Perl). Handles business logic and serves client side code and interfaces (HTML, CSS, Javascript)
* Client: * Client (Some in Android, Webview - HTML, CSS & Javascript)
* Server: * Yes, heavily server (Java/Perl). Handles business logic and serves client side code and interfaces (HTML, CSS, Javascript).
(Such as backoffice works - reconciliations, fraud checks, recommendation generations, Image optimizations) Or services (Service Orient Architectures)
* Client: * No
* Server: * Mainly server. No User Interface. Different Application Interfaces
Here we are going to talk about development life cycle of mainly server side applications. Specifically, we would like to take a practical example of deploying a Spark Application - which is a headless backend - an application which doesn't have a user interface.
Loading comments...