All new Google Analytics accounts can now only use Universal Analytics, which is now the officially supported version of Google Analytics. The classic "Google Analytics" referred to in this post is no longer recommended.
-Τρίτη, 6 Φεβρουαρίου 2018
Microservice Boundaries: 5 characteristics to guide your design
What’s new in Angular 5?
-Τετάρτη, 24 Ιανουαρίου 2018
ASP.NET Core MVC provide ways to reuse and share visual elements and common code between different views. These are 1) Layout Page 2) Start Page 3) Imports Page.
In the last few articles, we have seen how to work with asynchronous programming in C#. Although it is now easier than ever to write responsive applications that do asynchronous, non-blocking I/O operations, many people still use asynchronous programming incorrectly. A lot of this is due to confusion over usage of the Task class in .NET, which is used in multithreaded and parallel scenarios as well as asynchronous ones. To make matters worse, it is not obvious to everyone that these are actually different things.
ASP.NET Web API is a great piece of technology. Writing Web API is so easy that many developers don’t take the time to structure their applications for great performance.
In this article, I am going to cover 8 techniques for improving ASP.NET Web API performance.
Authentication for modern web applications is usually done in 2 major ways:
Token based authentication: this is usually done for APIs used by 3rd party developers. Client requests exchange a client id and secret key for an access token that they then pass in each request to the server to establish identity and claims.
Cookie based authentication: this is done for browser based web applications that have a web front end like views and pages. After the user signs-in, the server packages the user details into a cookie and sends out in the response. The browser then auto-sends the cookie back with each request so the user stays authenticated on the server. To keep the size of cookie within the 4KB limit, ASP.NET stores the details on the server in a Session object and just sends the session id back so that later it can look up the session in memory.
(This post is cross posted from https://fluin.io/blog/angular-best-practices-august-2017)
Another month, another summary of best practices. This month we’re back to some of the basics about tooling and IDE configuration, and some reactive programming principles that will set you up for future success.
This chapter describes and discusses high level patterns and principles commonly used for applications today. These are often referred to as the architectural styles, and include patterns such as client/server, layered architecture, component-based architecture, message bus architecture, and service-oriented architecture (SOA). For each style, you will find an overview, key principles, major benefits, and information that will help you choose the appropriate architectural styles for your application. It is important to understand that the styles describe different aspects of applications. For example, some architectural styles describe deployment patterns, some describe structure and design issues, and others describe communication factors. Therefore, a typical application will usually use a combination of more than one of the styles described in this chapter.
SDLC stands for Software Development Life Cycle. SDLC is a process that consists of a series of planned activities to develop or alter the Software Products. This tutorial will give you an overview of the SDLC basics, SDLC models available and their application in the industry.