CI (Continuous Integration) CI (Continuous Integration) means continuous integration. It is a process of automatically building and testing code whenever it is written and changed. Simply put, it is a process of automatically integrating code written by multiple developers. How CI Works A developer modifies code The code is pushed to a repository (e.g., GitHub) A CI tool automatically fetches the code and builds it It runs tests It notifies the developer with the results Benefits of CI Code issues can be found quickly The time for manually building and testing can be reduced High-quality code can be maintained CD (Continuous Deployment) CD (Continuous Deployment) means continuous deployment. It is a process of automatically reflecting the code that has passed through the CI process into a service. In other words, it is a process of making developed content available to users right away. ...

Sockets A socket is software that provides an interface for network communication. Sockets help facilitate communication between clients and servers, allowing them to send and receive data. Sockets offer an Application Programming Interface (API) for network communication. They work with both TCP (Transmission Control Protocol) and UDP (User Datagram Protocol), each providing a means to transfer data reliably. Socket Communication Methods Sockets provide the following methods to facilitate communication between clients and servers: ...

First-Level Cache First-level cache (L1 cache) is a cache that exists within the persistence context. When an entity is retrieved, the persistence context stores the entity in the cache. If the same entity is retrieved later on, the persistence context finds the entity in the cache and returns it. Hence, it is only valid within a transaction, and when the transaction ends, the first-level cache is also terminated. Dirty Checking Dirty checking is a way of tracking changes to entities using the first-level cache. When an entity is retrieved, the persistence context stores the initial state of the entity. If the state of the entity changes later on, the persistence context tracks the changes and reflects them in the database. ...

What is a Persistence Context The Persistence Context in Java Persistence API (JPA) refers to an environment that manages entities. It keeps track of entities and their state changes in relation to the database. The Persistence Context is handled by an Entity Manager. Key Functions of a Persistence Context Entity Management: An EntityManager manages entities. The Persistence Context stores the initial state of an entity. Transaction Association: The Persistence Context’s lifecycle is tied to a transaction. When a transaction is committed, changes made to entities managed by the Persistence Context are reflected in the database. Dirty Checking: ...

What is Dirty Checking? Dirty Checking is a mechanism in JPA (Java Persistence API) that automatically detects changes made to an entity and propagates those changes to the database. With Dirty Checking, developers can modify the state of an object without having to explicitly write database update queries. It’s important to note that Dirty Checking only applies to entities managed by the Persistence Context. How Dirty Checking Works Entity Management: Entities are managed by an EntityManager. The Persistence Context stores the initial state of the entities. Change Detection: Before a transaction is committed, JPA compares the current state of an entity with its initial state. Applying Changes: If any changes are detected, JPA automatically generates and executes database update queries. When the transaction is committed, the changes are propagated to the database. Example 1 2 3 4 5 6 7 8 9 10 11 12 13 // Saving the entity Member member = new Member("Alice"); memberRepository.save(member); // Retrieving the entity Member findMember = memberRepository.findById(member.getId()).get(); // Modifying the entity findMember.setName("Bob"); // Change detection // Dirty Checking kicks in and automatically generates and executes a database update query. // UPDATE member SET name = 'Bob' WHERE id = 1; Advantages Convenience: Developers only need to modify the state of the object, without having to write database update queries. Consistency: Data consistency is maintained as changes are automatically propagated to the database. Productivity: It improves productivity as developers can focus on business logic.