Documenting code, one commit at a time.
When building robust web applications with Spring Boot, one common challenge is preventing sensitive or unnecessary fields from leaking into your public API responses. In the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, we recently focused on cleaning up our data transfer objects to ensure that internal state isn't exposed to the client.
Building scalable web applications often starts with a simple goal: get the data on the screen. While working on Ryuu-no-Mi/Master-Spring-Boot-3-web-apps, I found myself refactoring the frontend layer to move away from bloated controller-driven views toward a more maintainable, component-based architecture.
Initially, my approach involved bundling business
In our current work on the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, we have been focusing on hardening the backend services that handle our product catalog. While utility classes and basic CRUD operations often seem trivial, keeping them clean is essential for long-term project health.
As a project scales, the ProductService layer often becomes a
In the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, I have been focusing on strengthening our application security. Specifically, I recently worked on implementing a robust JSON Web Token (JWT) authentication flow to manage user sessions effectively.
Traditional session management stores state on the server, which can become a
In our Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, we recently focused on hardening our application's perimeter by refining our security configuration. As our project grows, moving beyond basic defaults toward a more structured, granular security model has become essential.
With the expansion of our API endpoints, we faced the classic
In the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, maintaining clean data access logic is essential for application reliability. Recently, I focused on addressing inconsistencies in how we verify user existence within our data layer, specifically refining our usage of repository patterns.
When building web applications, a common requirement is checking
When working on the Ryuu-no-Mi/Master-Spring-Boot-3-web-apps project, the bridge between our Angular frontend and our Java backend relies on clear, robust communication via RESTful services. Connecting these two worlds is often where developers encounter the most friction, especially when dealing with data serialization and reactive streams.
Recently, our team working on the Ryuu-no-Mi/Inmotech-Backend project addressed a critical security and usability issue related to Cross-Origin Resource Sharing (CORS) in our OAuth 2.0 implementation. This fix was crucial for ensuring seamless and secure interactions between our decoupled frontend applications and the authentication server, preventing common browser-based security blocks.
In the Ryuu-no-Mi/Inmotech-Backend project, we continuously strive to improve the user experience, particularly in property search and filtering. A key aspect of this is how we present geographical data to users, allowing them to quickly narrow down their search by location.
Previously, our property
Our ongoing work on the Inmotech-Backend project, a core component of Ryuu-no-Mi's property platform, recently focused on significantly improving its property search capabilities. With a catalog exceeding 30,000 properties, the challenge was to offer highly accurate geographical filtering and a responsive user experience through dynamic search facets.
Previously, our search
