Mendix Advanced Developer case studies
Mendix Advanced Developer · Put your knowledge to work in context.
The Mendix Advanced Developer credential is the second-tier certification for professionals who already build Mendix applications confidently and now need to show they can design them for scale, security and reuse. It targets developers with roughly a year or more of hands-on project work - people who model domain logic daily, wire up integrations, and are moving from "make it work" to "make it maintainable." The exam is scenario driven: item stems describe a realistic application problem and ask you to choose the best approach. The Mendix Advanced Developer case studies are 5 cases and about 5,420 words.
1Northline Equipment Rentals: a three-year-old inheritance hierarchy
Northline Equipment Rentals runs a Mendix 10 application on a single PostgreSQL database. The domain model has a Vehicle entity (plate, dailyRate, notes) that is generalized into Car , Van and Truck ; Reservation is associated with Vehicle , MaintenanceRecord is associated with Vehicle , and Inspection exists only for trucks.
1,041 words, about 5 min2Meridian Staffing: an empty grid and a leaking export
Meridian Staffing built a Mendix application in which Placement records link a Candidate to a Client . Client is associated with AccountManager , a specialization of System.User .
1,127 words, about 6 min3Greenleaf Foods: a nightly import that loses the whole batch
Greenleaf Foods imports supplier price lists every night. A scheduled event calls SUB ProcessFeed , which retrieves an ImportBatch and loops over its up to 1,200 PriceLine objects.
1,045 words, about 5 min4Atlas Freight: a 60-second timeout and a partner who wants OData
Atlas Freight exchanges shipment data with a partner. Inbound, a REST endpoint returns shipments with nested packages - 4,000 shipments per page, 25 packages each, with a partner-mandated page size of up to 4,000.
1,109 words, about 6 min5Horizon Energy: a 47-second dashboard under a 2 GB heap
Horizon Energy's asset dashboard takes 47 seconds to open. The microflow ACT LoadDashboard retrieves all WorkOrder objects matching the XPath [Status != 'Closed'] - about 60,000 rows out of 380,000 - then loops over them, retrieving the associated Asset inside the loop for each work order and incrementing counters on a non-persistent DashboardStats object.
1,098 words, about 5 min