Book Image

Building Low-Code Applications with Mendix

By : Bryan Kenneweg, Imran Kasam, Micah McMullen
Book Image

Building Low-Code Applications with Mendix

By: Bryan Kenneweg, Imran Kasam, Micah McMullen

Overview of this book

Low-code is a visual approach to application development. It enables developers of varying experience levels to create web and mobile apps using drag-and-drop components and model-driven logic through a graphic user interface. Mendix is among the fastest-growing platforms that enable low-code enthusiasts to put their software ideas into practice without having to write much code, and Building Low-Code Applications with Mendix will help you get up and running with the process using examples and practice projects. The book starts with an introduction to Mendix, along with the reasons for using this platform and its tools for creating your first app. As you progress, you’ll explore Mendix Studio Pro, the visual environment that will help you learn Mendix app creation. Once you have your working app ready, you’ll understand how to enhance it with custom business logic and rules. Next, you’ll find out how to defend your app against bad data, troubleshoot and debug it, and finally, connect it with real-world business platforms. You’ll build practical skills as the book is filled with examples, real-world scenarios, and explanations of the tools needed to help you build low-code apps successfully. By the end of this book, you’ll have understood the concept of low-code development, learned how to use Mendix effectively, and developed a working app.
Table of Contents (18 chapters)
1
Section 1: The Basics
6
Section 2: Building Your First App
11
Section 3: Leveling Up Your App

Building functional modules

Each Mendix project is made up of a collection of modules. When you first create a project, it will contain a System module and a module named MyFirstModule. As the project grows, you will likely add more modules. You can think of modules as groupings of similar or related functionality. For example, you may have an application that is an online shop. Perhaps one module handles everything related to inventory, another module handles ordering, and another module handles customers and their data. The number of modules really depends on the project, how many different areas of functionality it has, and often times on the development team, as well as the guidelines and governance put in place at the company.

Notably, each module will contain its own domain model. As you are now aware of from the previous chapters and building out the example project, the domain model is your database (or data model) for the project. So far in the project, we have built out...