Advantages of Prism

Reusability: Prism allows building component in one framework (WPF) and reusing it in other platforms (Silverlight, Windows Phone). Project architecture should design in such a way.

Modularity: As everything is break down into modules, Prism supports modularity due to this PRISM is flexible, extensible .

Extensibility: Due to Prism design patterns nature new functionality that is to be added is easily extensible for future purpose.

Maintainability: The large scale complex applications developed using Prism are maintenance friendly.

Flexibility: Prism is flexible to develop large complex applications.

Team Collaboration: Simultaneous module development is possible and Multiple teams can work on different modules simultaneously.

Fault Tolerance: It allows components to be thoroughly and completely tested thus results in error free application development of better quality.

Comments

Javascript - Unanswered questions - Part 1

What is Event delegation? Event delegation is Javascript as it relates to the DOM. It basically means that if you attach an event listener to a DOM element that listener is not only firing on that DOM element. It's actually firing on every children in that. So, for instance if you have a navigation and so you've got an unordered list you've got list items and then you've got anchor tags inside that navigation what you have. If you add an event listener to the ul element in essence you're actually adding event listener to all of the children as well. In short, JS event listeners fir not only on a single DOM element but on all its descendants. What is Event Bubbling? It's actually inverse of Event delegation. Also known as propagation, events on an DOM element will bubble up and also fire on all parents. What's the difference between "target" and "currentTarget"? target is the actual element that triggered the event for example clicked, wh...

Microservices vs. APIs

It still surprises me just how many times I come across misconceptions around Micro Services and APIs. Often hearing phrases like micro services are fine grained web services or API is themselves are equivalent to micro services. These all sort of show fundamental misconceptions under the covers. So, I've written this just to really break that out and explain about what the key differences are in those two concepts. What is an API? An API, fundamentally Application Programming Interface, that is an interface. It's a way of making requests into a component. So it's the route that you go in to make those requests. In modern use that typically means a REST API, that's a call made using HTTP protocol using JSON data as the payload. What are Micro Services? So let's ensure we also have a clear crisp definition on what a micro service architecture really is. Micro-Services architecture is about breaking down large silo applications into smalle...

LOGANATHAN VELSAMY

Search This Blog