Being a .Net Developer and using the open technologies, I have lots of options of taking the advantage of the framework but once you started growing in your career, more then What technology you use? the question become How the technology is used ? and that is Architecture.
An architecture of a something you are implementing is very important once you start writing the code.
If you are writing a mobile application that needs to be cross browser compatible and can work on on any mobile device, you need to follow the modern architecture that is getting common across all the application.
The architecture should use SPA (Single Page Application) and REST api's and should be devoid of any stored proc to avoid complexity.
Let's start with why to use SPA,
A SPA is written in HTML5, JS, CSS3 and lots of other JS libraries.
The other JS libraries has some basic needed libraries like .less or .sass for css maintenance, Require JS for correct Integration of code and ofcourse Jquery, bootstrap to give a beautiful touch and underscore and Grunt runner to reduce the load of the developer and release manager.
What you needed the most is to decide what architecture you need to follow in client side, MVVM or MV* model.
I am a fan of MVVM if you know your model structure and it won't change in time, it represents concrete db design and architecture with a vision.
An MVVM model consist of Models, Views and View Models that handles your views lots of helper files and uses web API to communicate to server,
The MVVM architecture can be achieved using the Knockout JS which is an open source JS framework developed by a Microsoft employee.
The other is MV* model the * can be P or C where P is presenter and C is controller. This model is a standardized model and is followed as a standard practice by Microsoft and Ruby on Rails and can be achieved using Angular JS.
So your front end design you need to decide what your application can use, it has no relations to DB and it only needs the data to display on screen and need a way to post to server. So here comes the basic operations which are
CRUD - Create Read Update and Delete or POST GET PUT and DELETE.
These basic operations can be achieved from front end using the popular AJAX calls.
As the libraries that needs to be used to achieve your dream, now for back end you need to decide what you want to use.
I will suggest .NET rest api with entity framework, they have excelled in it, performance wise also or Ruby and php is also suggestible. But if performance is what you are looking for then node.js is the choice for you, but it has its own learning curve or rather its more towards unlearning.
.
So this is how I approach towards making an application, how you do it its all upto you but the basic remains the same.
And one more thing, you can achieve cross platform and cross device app with it as well, how? Because it is disconnected with your server All you need to do is to change the frame of your app and you can also use third party tool like phone gap.
Happy understanding
An architecture of a something you are implementing is very important once you start writing the code.
If you are writing a mobile application that needs to be cross browser compatible and can work on on any mobile device, you need to follow the modern architecture that is getting common across all the application.
The architecture should use SPA (Single Page Application) and REST api's and should be devoid of any stored proc to avoid complexity.
Let's start with why to use SPA,
A SPA is written in HTML5, JS, CSS3 and lots of other JS libraries.
The other JS libraries has some basic needed libraries like .less or .sass for css maintenance, Require JS for correct Integration of code and ofcourse Jquery, bootstrap to give a beautiful touch and underscore and Grunt runner to reduce the load of the developer and release manager.
What you needed the most is to decide what architecture you need to follow in client side, MVVM or MV* model.
I am a fan of MVVM if you know your model structure and it won't change in time, it represents concrete db design and architecture with a vision.
An MVVM model consist of Models, Views and View Models that handles your views lots of helper files and uses web API to communicate to server,
The MVVM architecture can be achieved using the Knockout JS which is an open source JS framework developed by a Microsoft employee.
The other is MV* model the * can be P or C where P is presenter and C is controller. This model is a standardized model and is followed as a standard practice by Microsoft and Ruby on Rails and can be achieved using Angular JS.
So your front end design you need to decide what your application can use, it has no relations to DB and it only needs the data to display on screen and need a way to post to server. So here comes the basic operations which are
CRUD - Create Read Update and Delete or POST GET PUT and DELETE.
These basic operations can be achieved from front end using the popular AJAX calls.
As the libraries that needs to be used to achieve your dream, now for back end you need to decide what you want to use.
I will suggest .NET rest api with entity framework, they have excelled in it, performance wise also or Ruby and php is also suggestible. But if performance is what you are looking for then node.js is the choice for you, but it has its own learning curve or rather its more towards unlearning.
 |
| Disconnected Architecure |
So this is how I approach towards making an application, how you do it its all upto you but the basic remains the same.
And one more thing, you can achieve cross platform and cross device app with it as well, how? Because it is disconnected with your server All you need to do is to change the frame of your app and you can also use third party tool like phone gap.
Happy understanding
Comments
Post a Comment
Important - Make sure to click the Notify Me check-box below the comment to be notified of follow up comments and replies.