Master and Slave Architecture in Jenkins


If we use one machine for jenkins then the moment we run multiple jobs it may burden the machine/vm which can lead to system crash 

To reduce burden on jenkins server/vm we can go with master - Slave configuration which could be used to reduce the burden on jenkins server/vm by distributing tasks/load.

Jenkins Master vs Jenkins Slave

The machine/server where jenkins tools is installed can be referred as master machine which is used to create jobs, schedule the jobs and mange the jobs 

It will also distribute jobs executions into slave machines/servers

Note: We can Run/execute jobs on jenkins Master machine too however it's not recommended

Jenkins Slave: 

It's a machine which is connected to jenkins master machine and execute the job/task assigned by master machine/server.

Slave server/machine will receive tasks from master machine for the job execution.




Comments

Post a Comment

Popular posts from this blog

Monolithic Architecture

Image
 Monolithic Architecture In our application, we will have several modules and several components are also available. Components are 1. Presentation Components These are responsible for handling Http Requests. Web applications means front end pages, Distributed applications means Rest Clients. 2. Web Components Responsible to handle user requests.(Servlets basically handles the Requests). 3. Business Components  Responsible to handle the business logic as per the business deals. 4. Persistence Components DAO is responsible for performing DB operations like DML,DDL,TCL,.... 5. Integration Components(Webservices, RestFul Services) Two projects can talk to each other only when we have Integration logic(basically RestfulServices, WebServices,...). 6. Authorization Components Responsible for Authorizing the user. 7. Notification Components Responsible for sending email or mobile message notifications. If we develop all these components as a single project then it is called as " Mono...
Read more

Advantages and Disadvantages of Monolithic Architecture

 Benefits of going for Monolith Architecture  Simple for development(becoz all are available in single project): At initial time it is very easy.   Easy for Testing : End to End Testing we can perform.   Easy for deployment : One war file only we have to deploy to server.   Easy for Scaling : multiple server we can spin easily(horizontal/vertical scaling) if requests increases then we can make keep multiple servers through which the scaling can be done to provide good responses to the client.  Disadvantages of Monolith Architecture  Maintenance of the application: If the application is to large and complex, it is difficult to understand. Change Request in the code is very difficult. Some changes in the existing application will have an impact to the other code, Lot of Impact Analysis will occur.   Adapting to New Technology is required: Change in java version and adapting to the version change also will take time. Applicati...
Read more

Spring AOP ( Aspect Oriented Programming )

  Cross-cutting concern: Separating the service logic from the business logic is called cross-cutting concern, Clear cut separation will be there. Terminologies of AOP: 1. Aspect: It is the class that provides additional services to the project like Transaction management, security, encode/decode, logging etc. Separating the business logic form the 3rd party service and keeping them in a separate class, that class we call it as Aspect: 2. Advices: Inside aspect, we write logic to give us the  3. Pointcut 4. JointPoint  5. Target 6. Weaving 7. Proxy ============= Need to dump few topics...coming soon =========== 1. BeforeAdvice: Before the business method, the particular advice should be selected and executed. 2. AfterAdvice: After the execution of business logic method,  that particular advice should be executed.  3. AroundAdvice: There will be 3 portions, before executing b.methods...some part of advice will be executed and then b.methods will execute and then...
Read more