kafka_2.13-3.9.0/bin/zookeeper-server-start.sh kafka_2.13-3.9.0/config/zookeeper.properties kafka_2.13-3.9.0/bin/kafka-server-start.sh kafka_2.13-3.9.0/config/server.properties
Angular, typescript, cypress, ngrx, rxjs, signals, react, node, mongodb, mongoose

yes we can acheive this by using named router-outlet, and in router congig we need to pass outlet
prop
Ex:
{path: '', component: '', outlet: left}
{path: '', component: '', outlet: right}
@Injectable root - Will download and create reference 1st time when component is used
providers [] in [App_Config] - services which are registered here will be loaded at app initial loading time, [which means] these services are ignored by Angular tree shaking and included in the initial bundle
provider [] in [Component] - will create multiple instance and references if we use this component based approach

[Injecting_Service_into_another_Service] - these 2 services can be registered as 1 or 2 approachees [MIX_AND_MATCH]
Note: student servie is created as approach 1 Now if i create Logger service and if i use 3rd approach to register Logger service in component and if i inject logger into student service then it will give null injector error
[VAR]
[ROUTING]
[SSR