Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microservice pattern: Server-side page fragment composition #2697

Open
iluwatar opened this issue Oct 15, 2023 · 2 comments
Open

Microservice pattern: Server-side page fragment composition #2697

iluwatar opened this issue Oct 15, 2023 · 2 comments

Comments

@iluwatar
Copy link
Owner

iluwatar commented Oct 15, 2023

Description:

The Server-Side Page Fragment Composition design pattern involves composing a webpage from various fragments that are managed by different microservices. This pattern is particularly useful for creating modular, scalable web applications where each part of the page can be developed, deployed, and scaled independently. The key elements of this pattern include:

  1. Fragment Composition: The server assembles the final webpage by composing various page fragments delivered by different microservices.
  2. Microservices: Each page fragment is managed by a separate microservice, responsible for rendering that specific fragment.
  3. Scalability and Independence: Each microservice can be developed, deployed, and scaled independently, enhancing the flexibility and maintainability of the application.
  4. Performance Optimization: By assembling the page on the server-side, the pattern can optimize performance by reducing the load on the client and improving response times.
  5. Consistent User Experience: Ensures a consistent user experience by composing fragments into a cohesive webpage.

References:

Acceptance Criteria:

  1. Implement a demo project illustrating the Server-Side Page Fragment Composition design pattern.
  2. Create separate microservices for different page fragments (e.g., header, footer, main content).
  3. Implement a server-side composition service to assemble the final webpage from these fragments.
  4. Ensure that each microservice can be independently developed, deployed, and scaled.
  5. Provide comprehensive documentation and examples demonstrating the use of this pattern.
  6. Adhere to the project contribution guidelines outlined in the wiki.
@Pat-r1ck
Copy link

can you assign me this one.

Copy link

stale bot commented Feb 1, 2024

This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale issues and pull requests that have not had recent interaction label Feb 1, 2024
@stale stale bot removed the status: stale issues and pull requests that have not had recent interaction label Mar 24, 2024
@iluwatar iluwatar added info: help wanted status: stale issues and pull requests that have not had recent interaction labels Mar 24, 2024
@stale stale bot removed the status: stale issues and pull requests that have not had recent interaction label Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants