You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are numerous articles on Strapi; however, they do not provide design principles or methodologies that can be leveraged to build scalable, strapi-dependent enterprise systems.
This tutorial will present an application on domain-driven design, a famous design pattern methodology in the development of a healthcare appointment application utilizing Strapi and Next.js.
What are the objectives of your article?
Introduction
Overview: What is domain-driven design?
Benefits of domain-driven design
Benefits of using Strapi
Setup
Setup the development environment (Node.js, pnpm, yarn).
Setup and configuration of a strapi project.
Setup of the frontend project
CMS architecture design
Create content types for
Users
Patients
Doctors
Appointment
Establish relationships between content types.
Appointment content relationships with patients
Appointment content relationships with doctors
Backend with Strapi
Create and model content types for users.
Set roles and permissions for users (patients, users).
Creating the frontend
Abstract business logic application into layers
Domain-specific (i.e., patient domain, doctor domain, appointment domain) layer
Application layer
Service layer (layer responsible for fetching data from Strapi)
View Layer (UI, Components Layer)
Authentication and authorization
Creation of an appointment by a patient.
Edit appointment by patient
View appointments made by patients.
Reject or accept an appointment by the doctor.
Advantages and disadvantages of utilizing the domain-driven design approach
Conclusion
What is your expertise as a developer or writer?
Advance
What type of post is this?
Tutorial
Terms & Conditions
I have read the Write for the Community program guidelines.
The text was updated successfully, but these errors were encountered:
Gitarackur
changed the title
Employing Domain driven design to building a Digital Health Application using Svelte and Strapi
Employing Domain driven design to building a Digital Health Application using Strapi and Next.js
Aug 19, 2024
What is your article idea?
There are numerous articles on Strapi; however, they do not provide design principles or methodologies that can be leveraged to build scalable, strapi-dependent enterprise systems.
This tutorial will present an application on domain-driven design, a famous design pattern methodology in the development of a healthcare appointment application utilizing Strapi and Next.js.
What are the objectives of your article?
Introduction
Setup
CMS architecture design
Backend with Strapi
Creating the frontend
Abstract business logic application into layers
Authentication and authorization
Creation of an appointment by a patient.
Edit appointment by patient
View appointments made by patients.
Reject or accept an appointment by the doctor.
Advantages and disadvantages of utilizing the domain-driven design approach
Conclusion
What is your expertise as a developer or writer?
Advance
What type of post is this?
Tutorial
Terms & Conditions
The text was updated successfully, but these errors were encountered: