Well, I don't like to call them Domain Specific Language
I like to call them Context Specific Language
Since Context is narrower then Domain.
Say you have a Backend System that support 3 kinds of user
Customer: Who use App or Web
They talk about :
Login, ListMyOrder, UpdateMyStatus, CheckMyReserveStatus, listMyGymClass,
Business Operator: Who use App or Web
They talk about :
howManyUserLoginToday, inventoryStatus, reportLastMonthSales, claimUserMessages, coachPerformance,
API Designer who use Web
We talk about:
checkTblConisitency, updateTblFieldsValue, archiveDBSince, backupDB, restoreTableFrom, aggregateLogData, removeDeadUser
These are all function name from My Backend API
They take parameters like (query,limit,skip)
ex. inventoryStatus({itemId:id,fromDate:date,toDate:date},100,0)
So,
I don't like restful crud style. Also not a fan of graphQL.
These function name help me think and organize the system.
Recent Comments