Apart from that, many service providers have had their SOAP web services to communicate with their customers and some are re-designing their API in REST-ful manner. Following a correct approach in designing the API is an important aspect of application architecture because consumers should be able to use the exposed api in a somehow standard way.
ASP.NET Core is so much influenced by the way Node.js applications are created.
We can follow every kind of performance tuning tips & tricks on server side code and on the database queries and indexes. But our application can perform better if it doesn\’t need to go through all those logic and have the response ready for the users.
This is partly can be done by utilizing caching mechanism.
the OutputCache attribute exists on System.Web.Mvc namespace and provides a simple and quick way for the developers to set their caching setting on any controller (or entire class if required).
public class HomeController: Controller
[OutputCache(Duration = 300, VaryByParam = "none)]
public ActionResult Index()
I read this great article about calculating CSS specificity value:
- If the element has inline styling, that automatically1 wins (1,0,0,0 points)
- For each ID value, apply 0,1,0,0 points
- For each class value (or pseudo-class or attribute selector), apply 0,0,1,0 points
- For each element reference, apply 0,0,0,1 point
Global Namespace Pollution
<!-- body -->