Leverage the CAM GUI to define Spring Boot microservice APIs, which unlocks Enterprise Grade, low code development. Here I will demonstrate using a GUI model editor to create a custom microservice with a single line of code.
Opening our sample CAM template, we see our User object with a nested Address:
By defining our data models visually, we only declare Repository interfaces in java code to indicate which node to expose1. When we run it, we see our 2 microservices registered with Eureka:
And then we can view data from the microsevice serving “User” data that contains the nested Address:
To run the demo, follow the readme instructions in our sample Spring Boot stack2. If you change the model in the CAM editor, upload your CAM template at the bottom of our homepage at Splicer.io. Our server will process your template and return client-server model artifacts. The readme in the Spring Boot stack explains how to deploy them.
Within CAM you can drag-and-drop your table structures into the left-hand-side of the tree, which represents data you want to expose in an API. The RHS of the screen correlates to your relational database schema. In our screenshot above, we show how those structures have been organized into data dictionaries as a way to normalize your data models3.
A major advantage of java-based systems is typesafety behind the scenes. Splicer extends typesafe entity classes out to compiled mobile clients. So first, we define the our model in CAM, and then the client and server compilers enforce those definitions.
Today, we have not only variance in client models and related microservices, but also mobile vs. web payloads as well. This means we need a way to normalize these models and automatically enforce them.
I will post a video demonstrating all of this in action soon.