Today we are going to see about the Monolith services vs Micro services and what are the key differences between them , advantages over one another, and finally specific purpose for each one. Monolith Services: In simple terms, Monolith services are widely used technology in current software world, a traditional monolith service essentially runs in a single platform, a single stack which holds all the business logic and data access logic placed in a single service, also in most cases the UI, Business Logic and Data access layers are tightly coupled and deployed in a single machine, this may be available to scale but this is strictly stick to its own stack / platform Advantages of Monolith: We can really get a lot of advantages for using Monolith services, * Single code base (This is an advantage until the code base isn't growing enormously) * No need to talk to other internal services to do a particular task as everything is available within * Single stack / platform is neede
Posts
Normally We will use the *ngIf to show hide the controls by using following method <div *ngIf="showIf" > <p> Showing the if part </p> </div> Where showIf needs to be declared in the component.ts file and it needs to be set as true in order to view that control Like this showIf : Boolean; in the constructor or in the ngIf this. showIf – true; For Else we need to create a ng-template and call in the else part like below Please Note: the ng-template’s id should be unique <div *ngIf="showIf; else elsePart"> <p Showing the if part </p> </div> <ng-template #elsePart> <p> Showing the else part </p> </ng-template> Example Source can be found at : https://angular-ivy-5vysbz.stackblitz.io
Angular: Constructor vs ngOnInit, Basic differences Constructor is the feature provided by ES6 (i.e. Typescript) ngOnInit is provided by Angular itself interface OnInit { ngOnInit(): void } Before seeing what was the order of execution let’s see if both is not available what will happen, You can see that the Angular s happily compiling and executing the code even the constructor or ngInit is not present As a next step we are trying to implement the ngOnInit interface explicitly, let’s see what will happen We are getting the following error Class 'AppComponent' incorrectly implements interface 'OnInit'. Property 'ngOnInit' is missing in type 'AppComponent' but required in type 'OnInit'. So we need to implement the ngOnInit if we are specifying in the class After implementing the ngOnInit we are getting the page back to normal So what is t