21
نموذجاً للبيانات
منصّة · 2025 · دون ذكر اسم العميل
حساب واحد للنزيل يجمع ثلاثة أعمال في المكان نفسه، فمن يقيم في الفندق ويستخدم النادي والمطعم يبقى له حساب واحد.
21
نموذجاً للبيانات
3
أنظمة فرعية
hotel, gym, restaurant
541
Technical README
lines, with diagrams
المشكلة
A hotel also operating a gym and a restaurant had three systems and therefore triple data entry, with no unified view of a guest who used all three. Cross-subsidiary charging is the specific thing that breaks: a guest signs for lunch and the charge needs to reach their room folio.
الحلّ المعتمد
Twenty-one interlinked models across the three subsystems sharing one guest identity, so hotel stays, gym membership and restaurant billing all resolve to the same person and the same folio. An admin frontend served directly from the API, plus a technical README with diagrams, because a system this interlinked is unmaintainable without one.
بنية النظام
Shared guest identity across three subsystems, with charges from any of them able to post to a single folio.
ومع كل قرار ثمنه
القرار الذي لا يُذكر ثمنه مجرّد تفضيل شخصي.
01
السبب
The cross-subsidiary charge is the reason the client wanted one system. Separate identities per subsystem means matching people by name, which fails on the first duplicate.
الثمن
The guest model has to satisfy three different sets of requirements, making it the most constrained entity in the schema.
النتيجة
One guest record follows the customer across all three businesses, and management sees consolidated revenue instead of three partial pictures.