Getting Started‎ > ‎

Evaluate API Creator

As an API Creator evaluator, you want to get a quick sense of what it does, its value proposition, and how it differs from other alternatives. Use the topics in this page to evaluate API Creator.

What problem does API Creator Logic address?

REST/JSON-based APIs are an accepted approach for mobile, cloud-based partnerships, and participation in an Enterprise Service Bus. The APIs require security and integrity support for transactional data exposed through public APIs. These elements often constitute half the app for update oriented database applications.

The following issues directly affect business agility and total cost of ownership (TCO):

  • Time to market. Logic is built manually, without automation tools such as UI frameworks.
  • Agility. Even if you address the time issue with lots of programmers, maintenance agility remains a problem. It is tedious and time-consuming to understand thousands of lines of code, their interdependencies, and their optimizations.

What is Live API Creator?

Live API Creator provides APIs for REST/JSON-access to database data, with unique spreadsheet-like declaration of transactional business logic and security. Live API Creator is browser-based API creator that does not require an integrated development environment (IDE). You define your resources, logic, and security using Live API Creator.

You specify the transactional logic that Live API Creator addresses. It automates complex, multi-table business logic and multi-table derivations. Live API Creator fine-grains security down to the row and column-instance level.

What is the Value Proposition?

API Creator provides the following strategic value for your organization, beyond enabling mobile and cloud access by way of REST:
  • Time to market. The automation of logic and security means that the server aspect of your application (often half the total) is reduced by orders of magnitude. This simple example shows how 5 rules replace 500 lines of code.
  • Reduced Total Cost of Ownership. The 5/500 savings translate directly into TCO
  • Agility. Automation for dependency management and SQL access means that the five rules express the equivalent of 500 lines of procedural code.
  • Reactive Logic. Logic is automatically injected into all transactions making re-use automatic and thereby eliminating an entire class of bugs.
  • Transparency. Business users can read the logic, understand system behavior, and assist in spotting errors or omissions.

How does Live API Creator fit into my architecture?

API Creator automates the rest interfaces, the data access, and the security/business logic for transactional applications. While the automation is wide in scope, it is designed to fit into an Enterprise architecture.

What about Real World complexity?

The example communicates the point as simply as possible. Your application likely contains more complicated requirements, so it is important to understand whether these are addressed.

API Creator automates Advanced Examples with remarkable power, including:

  • A Bill of Materials Price Rollup with four rules (a bolt is used in a Wing, Engine, etc - how does a price change affect the cost of a plane?)
  • A Bill of Materials Part Explosion with three rules (how many bolts remain in stock after building n planes?)
  • An Allocation of a Payment to a Customer with four rules (which Purchase Orders are paid off, and what is the resulting balance?)
  • Copy examples, such as auditing or cloning a Purchase Order and its Line Items
Beyond the pre-supplied rule types, you can extend the Logic Engine, so you can use server-side Javascript and define your own rule types.

How do I get started?

Get started by installing and connecting to a database. Your base tables are exposed as resources so you can begin client development in parallel with logic development. You can migrate these to defined resources for database insulation and latency reduction.

You do not have to expose your entire database or rewrite existing logic. Expose the data you wish by defining resources and define its logic and security.

What about Architectural issues: performance, extensibility, debugging?

Multi-table logic is optimized to optimize and eliminate SQL operations. Logic and SQL handling are extensible and debuggable

Quick Links

You can explore the following links: