Book Image

Rapid Application Development with OutSystems

By : Ricardo Pereira
Book Image

Rapid Application Development with OutSystems

By: Ricardo Pereira

Overview of this book

OutSystems is a software development platform that speeds up the build phase by abstracting code and making almost everything visual. This means replacing textual language with visual artifacts that avoid lexical errors and speed up code composition using accelerators and predefined templates. The book begins by walking you through the fundamentals of the technology, along with a general overview of end-to-end web and mobile software development. You'll learn how to configure your personal area in the cloud and use the OutSystems IDE to connect with it. The book then shows you how to build a web application based on the best architectural and developmental practices in the market, and takes the same approach for the mobile paradigm. As you advance, you'll find out how to develop the same application, and the great potential of reusing code from one paradigm in another and the symbiosis between them is showcased.The only application that'll differ from the application in the exercise is the one used in business process technology (BPT), with a focus on a common market use case. By the end of this OutSystems book, you'll be able to develop enterprise-level applications on the web and mobile, integrating them with third parties and other systems on the market. You'll also understand the concepts of performance, security, and software construction and be able to apply them effectively.
Table of Contents (21 chapters)
1
Section 1: OutSystems 101
5
Section 2: The Magical Path of the Backend
10
Section 3: Create Value and Innovate with the Frontend
16
Section 4: Extensibility and Complexity of the OutSystems Platform

Summary

In this chapter, we learned that it is important to design a robust, scalable, performant, and secure application, in order to support the growth of solutions, both in volume and in complexity.

We learned that we can do this by applying an architectural model called the Architecture Canvas (or 3 Layer Canvas), and we examined its layers and sub-layers and what types of modules fit into each of them.

In addition, we analyzed the process of designing an architecture, including its steps (disclose, organize, assemble, and iterate through them as often as necessary) and which rules and principles serve as a foundation for this process. We saw some refactoring techniques to align the architecture with the expected model and mentioned some useful tools for OutSystems architecture support.

But how much further can we go? Now that we have figured out how to build our "home," how far can we go? Can we "stretch" the OutSystems universe beyond what already...