Differences

AngularJs

Factory and Services.

References:https://blog.thoughtram.io/angular/2015/07/07/service-vs-factory-once-and-for-all.html

The difference between services and factories

we can define a service like this:

app.service('MyService', function () {

  this.sayHello = function () {

console.log('hello');

};

});.service() is a method on our module that takes a name and a function that defines the service.

app.factory('MyService', function () {
  return {
    sayHello: function () {
      console.log('hello');
    }
  }
});.factory() is a method on our module and it also takes a name and a function, that defines the factory.
 a service is a constructor function where as a factory is Not .There’s 'this' code that calls Object.create()with the service constructor function, when it gets instantiated. However, a factory function is really just a function that gets called, which is why we have to return an object explicitly.
. That basically allows us to do some configurationstuff or
 conditionally create an object or not, which doesn’t seem to be possible when creating a service directly, which is why most resources recommend to use factories over services

WHAT IS A REST API?


REST (Representational State Transfer) is truly a “web services” API. REST APIs are based on URIs (Uniform Resource Identifier, of which a URL is a specific type) and the HTTP protocol, and use JSON for a data format, which is super browser-compatible. 


WHAT IS SOAP?


SOAP (Simple Object Access Protocol) is its own protocol, and is a bit more complex by defining more standards than REST—things like security and how messages are sent. These built-in standards do carry a bit more overhead, but can be a deciding factor for organizations that require more comprehensive features in the way of security, transactions, and ACID 


REST


RESTful web services are stateless. You can test this condition by restarting the server and checking if interactions survive.
For most servers, RESTful web services provide a good caching infrastructure over an HTTP GET method. This can improve the performance if the information the service returns is not altered frequently and is not dynamic.
Service producers and consumers must understand the context and content being passed along as there is no standard set of rules to describe the REST web services interface.
REST is useful for restricted-profile devices, such as mobile, for which the overhead of additional parameters are less (e.g., headers).
REST services are easy to integrate with existing websites and are exposed with XML so the HTML pages can consume the same with ease. There is little need to refactor the existing site architecture. As such, developers are more productive because they don't need to rewrite everything from scratch; instead, they just need to add on the existing functionality.
A REST-based implementation is simple compared to SOAP.



SOAP


The Web Services Description Language (WSDL) describes a common set of rules to define the messages, bindings, operations and location of the service. WSDL is akin to a contract to define the interface that the service offers.
SOAP requires less plumbing code than REST services design (e.g., transactions, security, coordination, addressing and trust). Most real-world applications are not simple and support complex operations, which require conversational state and contextual information to be maintained. With the SOAP approach, developers don't need to write plumbing code into the application layer.
SOAP web services, such as JAX-WS, are useful for asynchronous processing and invocation.
SOAP supports several protocols and technologies, including WSDL, XSDs and WS-Addressing.


Reference :https://www.dotnettricks.com/learn/webapi/difference-between-wcf-and-web-api-and-wcf-rest-and-web-service

Web Service


It is based on SOAP and return data in XML form.


It support only HTTP protocol.


It is not open source but can be consumed by any client that understands xml.


It can be hosted only on IIS.



WCF


It is also based on SOAP and return data in XML form.


It is the evolution of the web service(ASMX) and support various protocols like TCP, HTTP, HTTPS, Named Pipes, MSMQ.


The main issue with WCF is, its tedious and extensive configuration.


It is not open source but can be consumed by any client that understands xml.


It can be hosted with in the applicaion or on IIS or using window service.



WCF Rest


To use WCF as WCF Rest service you have to enable webHttpBindings.


It support HTTP GET and POST verbs by [WebGet] and [WebInvoke] attributes respectively.


To enable other HTTP verbs you have to do some configuration in IIS to accept request of that particular verb on .svc files


Passing data through parameters using a WebGet needs configuration. The UriTemplate must be specified


It support XML, JSON and ATOM data format.



Web API


This is the new framework for building HTTP services with easy and simple way.


Web API is open source an ideal platform for building REST-ful services over the .NET Framework.




Unlike WCF Rest service, it use the full featues of HTTP (like URIs, request/response headers, caching, versioning, various content formats)


It also supports the MVC features such as routing, controllers, action results, filter, model binders, IOC container or dependency injection, unit testing that makes it more simple and robust.


It can be hosted with in the application or on IIS.


It is light weight architecture and good for devices which have limited bandwidth like smart phones.


Responses are formatted by Web API’s MediaTypeFormatter into JSON, XML or whatever format you want to add as a MediaTypeFormatter.



To Whom Choose Between WCF or WEB API


Choose WCF when you want to create a service that should support special scenarios such as one way messaging, message queues, duplex communication, etc.


Choose WCF when you want to create a service that can use fast transport channels when available, such as TCP, Named Pipes, or maybe even UDP (in WCF 4.5), and you also want to support HTTP when all other transport channels are unavailable.

What is SSL in asp net?





The HTTPS protocol is more secure than HTTP protocol because it includes the Secure Sockets Layer/Transport Layer Security (SSL/TLS) protocol. It is a more secure way to send a request to the server from a client, also the communication is purely encrypted which means no one can understand what you are looking for.



What is SSL
Secure Sockets Layer (SSL) is the standard security technology for establishing an encrypted link between a web server and a browser. This link ensures that all data passed between the web server and browsers remain private and integral. SSL is an industry standard and is used by millions of websites in the protection of their online transactions with their customers.

For SSL connection a web server requires a SSL certificate. Your web server creates two cryptographic keys, a Private Key and a Public Key.

The Public key does not need to be secret and is placed in a Certificate Signing Request (CSR) that is a data file also containing your details like your domain name, your company name, your address, your city, your state and your country. It will also contain the expiration date of the Certificate and details of the Certification Authority responsible for the issuance of the Certificate. This information is submitted to the CSR. During the SSL Certificate application process, the Certification Authority will validate your details and issue an SSL Certificate containing your details and allowing you to use SSL. Your web server will match your issued SSL Certificate to your Private Key. Your web server will then be able to establish an encrypted link between the website and your customer's web browser.

Reference :https://www.c-sharpcorner.com/UploadFile/225740/what-is-ssl-and-how-to-implement-in-Asp-Net-web-aaplication/