Why Workfusion Is Different by Design, and Why It Matters

In workfusion, a massive part of my time is spent describing how we’re different from design. There’s a very long list of factors we make to explain our different strategy, but in the heart the most important difference between workfusion’s cloud applications and conventional enterprise applications is the way we have created the object model the center of our structure.

We use the object model to specify both the construction of the applications (classes, associations, and characteristics) in addition to the logic of our applications (methods). All parts of the object model are described as metadata. Instead of those thousands of relational tables and millions of lines of code used to specify traditional business software, workfusion applications consist of countless of metadata definitions. Workday employs a relational database to store all metadata and all application data. To maximize application performance, Workday retains all application metadata and many application data in memory.
Possessing the application arrangement characterized as metadata means the arrangement of workfusion applications can be altered without needing to restructure the database. Having application logic described as metadata means that logic could be altered with no coding or recompiling code. Not utilizing the database to represent the arrangement of the applications dramatically lowers the amount of tables required to encourage them.
While the “how” part of this narrative is intriguing, I’d love to concentrate more on the “why” questions behind our structure. Why take another strategy, and why does this matter? The solution includes four crucial areas for the two Workday and also our customers: speed, safety, insight, and alter.
When you think of what is traditionally called business resource-planning systems (ERP), rate is most likely not the very first thought that springs to mind. However, when you’re a startup which has made a decision to compete against big ERP software vendors, you really do consider the necessity to move fast. We started Workday in 2005 with the object model, enabling us to significantly accelerate application development. For this day, programmers can quickly change Workday applications without needing to worry about changing the underlying database, or performing some other database management operations since they construct new features and products.
This is the way we are able to supply customers with three Workday upgrades each year instead of the industry standard of 1 year or more for conventional software updates. We can immediately respond to new customer requirements, and also the shorter development cycle enables customers more readily participate as design partners. (Waiting 1 years or more to understand your thought make it in to production could put off even the most enthusiastic customer, and with Workday the payoff could occur within four weeks.)