📄️ API Documentation
As described in the Architecture/System design section, pharmacy service is built using Domain Driven Design so it’s API endpoints, Management service is built using the common rest API method, here are examples of the two ways:
📄️ Architecture
The Diagram below explains a lot! According to requirements that are elicited from the pharmacist, a tailored solution is built for it using microservices architecture that its most used components are ready to scale horizontally and independently, and the same for downtime! and also for better logic isolation while going through complex and detailed business logic!
📄️ Infrastructure
The Pharmacy System’s infrastructure is built with Kubernetes to avoid vendor lock traps in any of the cloud services, it is 100% self-managed and migratable!
📄️ Design Patterns
Here some of used design patterns with explaining the problem they are solving, and how it is solved:
📄️ Tech Stack
As described in the architecture and design patterns sections, this solution cares a lot and is built to be loosely coupled, so the used tech stack can be replaced easily without causing overhead while refactoring in case a drift in business logic or requirements occurs.