If you’re trying to expand your enterprise code coverage to include mobility, you’ve come to the right place. We use either your database schema, or server model to generate native Android and IOS entity classes. These objects then become the client’s interface to your backend — thereby extending the object-relational (ORM) paradigm to the mobile coder.
NoSQL Data Agility:
Additionally, our structured models provide relational data agility typically associated with NoSQL. Static data type-checking enables rapid, NoSQL-paced coding, and keeps your pipeline working smoothly as it evolves. At last, you can incorporate agile models directly into distributed, compiled code!
This is all possible via our open source server that forms a “bridge” between your clients and your server model or database. The server also comes with a GUI that allows you to manage the relationship between your client models and your server model.
Here at Splicer, we realized that as expand our capabilities toward enterprise mobility, the fundamental complication we face is the ability to map various client models to a server model. This may not be obvious at first, but once it is fixed, you will find that mobile development is a breeze. And having the ability to graphically view these model relationships and what data is exposed to your clients is a big help.
How does it work?
Our declarative models expidite the manufacture of structured data artifacts. These artifacts securely connect native mobile apps to complex cloud applications. Such automation simplifies how companies build vital, secure, and high performance data pipelines.
To get started, Splicer tools ingest your database schema and provides a drag-and-drop UI for single-source access, object modeling, and generation of data model artifacts. Conceptually, we leverage a “model schema” to extend declarative models out to “the edge”. By exposing business semantics directly to native mobile clients, we convert Spring-based java servers (Spring Boot, Spring Data) into typesafe, full-stack, data pipelines. Mobile coders can then access DAOs directly on the clients — providing true full-stack, native enterprise mobility.
Why is it different?
With Splicer, the client’s data objects are typesafe and guaranteed to correlate to your server model. These client DAOs allow the mobile developer to access the server’s database just like a server-side ORM does. When you change your model, compilers show where your client code breaks due to model changes. If you have multiple types of mobile apps, this type of Model Management will save your sanity.
GUI visualizes the bridge between client objects and structured data. This expands your server model to readily unlock native enterprise mobility.
• Server coding optional
• Visually control the relationship between client object databases and the backend
• Re-use server model objects to develop sets of apps
• Audit data structure details to minimize payloads
• Compatible with the mobile databases such as Realm
• Supports synchronization