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

Bug: correction needed for Frontend and Backend technology classification in Microservices section #101

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rospllab
Copy link

In the provided documentation under the "Development" section of the Pre-Production phase (Microservice architecture), there appears to be a misunderstanding in classifying frontend and backend technologies. Specifically, it incorrectly lists "Node.js or React" as popular choices for frontend development. This needs correction to accurately reflect common practices and technology use in microservices architecture.

Detailed Analysis:
Incorrect Classification:

Node.js is a runtime environment that is primarily used for backend development. It allows developers to use JavaScript to write server-side code, making it popular for building scalable and efficient backend services in microservices architecture.
React is a JavaScript library used for building user interfaces (frontend). React is not typically used for backend development.
Correct Classification:

Frontend Development:
Technologies commonly used: React.js, Angular, Vue.js.
Purpose: Building the user interface and client-side logic.
Backend Development:
Technologies commonly used: Node.js, Java, Python, Go, .NET.
Purpose: Handling server-side logic, database interactions, and API endpoints.
Suggested Changes:
The corrected text should accurately separate frontend and backend technologies, reflecting their actual use cases in microservices development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant