Every Genesis application is different, but all Genesis applications share a common architecture. The best way to understand the purpose of all the main elements of this architecture is to familiarise yourself with the server modules and the web front-end.
The fields dictionary is where you specify all the fields you need for your data model.
Tables of data will be critical to your application, from simple tables of currencies or locations to more complex ones that contain trade or order information (for example).
Whereas tables tend to be groups of related information, a view is a way of looking at data - in many cases, literally. If you want to show all the trades you have done, then you might want to take some of that data from a table of trades, but you might want to add data from one or more other tables - currency details or counterparty IDs, for example.
This day covers:
Workstation set-up
Creating financial markets technology today is fundamentally broken – too slow, expensive and high-risk. Genesis is revolutionising software delivery within the financial markets so that any coder can create reactive, performant and compliant applications in days.
What you'll learn
Introduction
Creating a new component
There is a lot of technology embedded in the Genesis low-code platform. So, inevitably, we have to refer to it in this documentation.
Now that you have completed the Quick Start and are comfortable with the basics, it is time to build an advanced application that will demonstrate more features of the platform.
It is important to know that the Genesis low-code platform uses system-generated versions of these system files.
Let us now mention another important system file, Genesis Router. The Genesis Router module controls the routing of the messages between the back end and the front end of your application. You can configure this in the file genesis-router.kts.
The system-definition file, genesis-system-definition.kts, is the basis of all the configurations, scripts, data models, etc.
Now let us consider a few files that are vital for configuring your application.
Every application must have a -service-definitions.xml file. This is where you specify the ports of the various processes. The ports are used to communicate internally between these various processes.
What is the Genesis low-code platform?
Once you are happy with your data model, you can build your database.
With a database and two modules (a Data Server and an Event Handler) in place to supply data to the front end, we can now build our server.
So how would you go about creating something like that?
Now, let's just take stock.
There are some simple commands that enable you to start and stop your server.
Here is an edited example of a source file of issuance data from the Bloomberg feed.
Some feeds provide static sets of data that you can download for processing by your application. A good example is traded data from an exchange. This exercise shows you the key points for loading these data files. In this case, we shall use Bloomberg issuance data. We shall load this, parse it to reformat it to Genesis format, then place it in a staging table in a Genesis application. Once it is in the staging table, the data can be passed to other tables within the application.
If you are loading static data from an external site, this page gives more detail on the SFTP method for obtaining the data. It also looks at how you could deal with encryption and decryption in higher environments.
A Data Server supplies real-time (streaming) data to the front end of your application.
A Request Server supplies static data to the front end of your application.
Applications must respond immediately to different types of input: inputs from users, messages from other systems, market-data updates and internally calculated analytic signals. These inputs are events.
Application modules
In this tutorial you saw how to integrate with an external PostgreSQL server using the Genesis Data Pipeline configuration.
Create new Genesis project
In this part of the tutorial we will declare the PostgreSQL server as a data source and map the incoming rows to a Genesis Table object.
To deploy your application to your local Linux or WSL environment, see this guide.
The source data comes from a PostgreSQL server that has to meet the minimal configuration mentioned here.
You can run our Quick Start from a lightweight set-up. However, to set up a full-functioning developer workstation, you need to check out the hardware and software requirements in this section. This will get you fit to do some serious work.
Seed and Genx
The Genesis platform provides a Gradle plugin that makes it easy to perform all the installation tasks that are necessary to deploy your own Genesis project on your local workstation, from your IDE.
If you don't have a Linux box for running your Genesis platform, you can use Windows Subsystem for Linux (WSL2) to install a Linux environment on your Windows machine.
To install the Genesis low-code platform on your server, go through the following steps.
So far, you have a table; now we want to be able to see its content and create new entries.
The application has three files that contain vital configuration information:
Before you start, make sure you have checked out the hardware and software requirements.
Now let's create a single page with a grid and a form for entering data.
Now you are ready to define the fields and tables that make up your data model. This model structures information in a simple way that can be viewed by users and processed by the application.
Workstation set-up
Welcome to the quick start tutorial page. Here we are going to create a very simple application using some basic features of the Genesis Platform.
Credentials to login
The very simple application you will build will look like this:
This day covers:
This day covers:
This day covers:
This day covers:
This day covers:
Environment set-up
What you'll learn
To give your front end a wide range of visual possibilities, the Genesis low-code platform provides a wide range of Web Components. These are built on top of Microsoft FAST.
In financial organisations everywhere, there are spreadsheets that are effective tools, but which pose a significant operational and compliance risk.
Once you have the Genesis low-code platform, you can develop and deploy your own applications at speed, from the simplest of internal systems to complete exchanges.
You don't have to be bound by your existing systems at all. If you have a need for a new application, which looks too ambitious for now, the Genesis low-code platform could make that a realistic proposition in a realistic timeframe.
You can build complete new trading platforms that integrate with multiple internal and external systems. These are applications with clear user interfaces, highly sophisticated features; they can be specified and built to meet exactly the security and regulatory requirements you require.
Self-contained systems (aren't you bored by the term "silo") remain a big blocker for anyone looking for efficiency.