Designing a time axis for HR systems involves choosing between an interval model that stores start and end timestamps and an effective‑date model that uses effective dates and sequences, each affecting query simplicity, maintenance effort, common pitfalls, and ultimately enabling accurate historical and future employee data analysis.
This article details 58.com's end‑to‑end process of researching, defining, designing, and launching a proprietary HR management platform to replace foreign solutions, highlighting user research, MVP methodology, emotional design, and rapid delivery within an eight‑month timeline.
This article recounts how adopting agile practices—including user‑experience mapping, sprint‑0 preparation, iterative planning, daily stand‑ups, demo sessions, and retrospectives—dramatically improved delivery speed, quality, and business involvement for a corporate HR system project.
The article describes how Meituan applied the micro‑frontend concept to transform its HR system into a class‑single‑page application, detailing the shortcomings of iframe integration, the design of a portal project, application registration, routing, CSS scoping, JavaScript library version control, and the build‑and‑deployment workflow.
Meituan’s HR platform adopts a micro‑frontend architecture where a central Portal container registers isolated sub‑projects via a global route array, namespaces CSS, unifies shared libraries through a custom require system, and deploys static assets with PM2, delivering a single‑page experience, independent releases, and minimal bundle overhead.
This article details Alibaba's migration from Oracle PeopleSoft HCM to a self‑developed, cloud‑native eHR platform, describing the technical challenges, phased development using Groovy and MaxCompute, and the resulting six‑fold speed increase, hundred‑fold cost reduction, and enhanced employee experience.
