Useful Links

Sizing MicroServices

Micro Asynchronous HTTP microservices

PaaS-architectural-considerations

Docker-machine-compose-and-swarm-how-they-work-together

Cloud-native-application-platforms-structured-and-unstructured

Integrating Angular 2 and SignalR

Using TypeScript with Node.js+ExpressJs

Top companies using nodejs in production

Advertisements

Never mix HTML DOM manipulation code and AngularJS code

One of the key mistakes that is made by developers new to AngularJS is using HTML DOM manipulation code and AngularJS code together. Though may work sometimes, this would turn out to be a serious problem in some cases.

Consider the following example where we are creating list of items using ng-repeat in the HTML Template.

Record value is : {{record.value}}

 

However we also have the following  code inside the AngularJS controller that sets the CSS class for the labels dynamically created using ng-repeat.

for (var index in records)

{

document.getElementById(“ectdqa”+index).className = “highlight”;

}

This code inside the controller may work sometimes and may not work sometimes. The reason being, the code inside the controller might try to set the CSS class even before the control is created by the ng-repeat command.

The correct way would be to set the highlight flag inside the model and use the model during ng-repeat to set the CSS Class.

ASP.Net – Things to take care during deployment

  1. Although tracing is a great feature and provides added value when developing and debugging ASP.NET
    applications, it has some effects on the overall performance of the application, due to the tracing mechanism
    and the collection of data which is performed on each request. Therefore, if you have enabled tracing during
    development, turn it off before deploying your web application to the production environment, by changing the
    trace settings in the web.config:
    <configuration>
    <system.web>
    <trace enabled = “false”/>
    </system.web>
    </configuration>

SSL HandShake in F5 Load Balancer BIG-IP System

SOL15292 – Troubleshooting SSL / TLS handshake failures

The BIG-IP system offers several ways to manage SSL traffic:

  • SSL passthrough: The virtual server is configured to listen for SSL connections on a port, such as 443, but does not terminate the SSL connection. Under this configuration, the BIG-IP system passes the encrypted requests to the pool members.
  • Client SSL profile: The virtual server references a Client SSL profile, which enables the BIG-IP system to accept and terminate client SSL requests. Using this configuration, the system decrypts SSL client requests, and then sends the requests to the server. The system then re-encrypts the server responses before sending them back to the client.
  • Server SSL profile: The virtual server references a Server SSL profile, which enables the BIG-IP system to initiate secure connections to the SSL servers.
  • The SSL proxy feature: The SSL proxy feature allows the BIG-IP system to optimize SSL traffic between the client and the destination server without terminating the SSL connection.

If you have configured the BIG-IP system to process SSL connections using one of the previous methods, there may be occasions when you need to perform troubleshooting steps related to the SSL handshakes. Before troubleshooting the SSL handshake, it is helpful to review the handshake protocol.

SSL handshake overview

SSL communication consists of a series of messages exchanged between two parties (client and server). The SSL handshake between a client and server consists of nine steps, and appears as follows:

Detailed Description on F5 Handshake