Home‎ > ‎

Evaluation Guide

Espresso Logic Evaluators can use this page to get a quick sense of what Espresso Logic does, its value proposition, and how it differs from other alternatives.

What problem does Espresso Logic address?

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

And there are issues that directly affect business agility and 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 Espresso Logic?

Espresso Logic provides Web Services for REST/JSON access to database data, with unique spreadsheet-like declaration of transactional business logic and security. It is provided as a service, so there is nothing to install.  No IDE is required; you simply use the Logic Builder via the Browser to define your Resources, Logic and Security.

The transactional logic addressed by Espresso Logic, while simple to specify, is remarkably powerful.  It automates complex, multi-table business logic - not just multi-field/multi-table validations, but more importantly, multi-table derivations.  Security is fine-grained, down to the row and column-instance level.

What is the Value Proposition?

Espresso Logic was designed to provide strategic value for your organization, beyond enabling mobile and cloud access via 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 - automated dependency management means that maintenance consists simply of changing the rules.  You bypass the tedious archaeology of deciphering existing code to determine where to apply changes - a challenge that cannot be met by simply adding resources.

  • Active Integrity - automatic re-use means that logic is automatically applied without requiring specific calls, so integrity is always enforced.  Compliance officers can verify integrity simply by reviewing the rules, instead of trying to verify the correctness of hundreds of thousands of lines of code.

  • Transparency - logic is specified in concise business terms, so that business users can understand them and help reduce requirements risk.  Logic is both transparent documentation and maintainable implementation, creating a corporate resource for understanding and agility.

How does it fit into my architecture?

Espresso Logic 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 above is designed to communicate the point as simply as possible.  But of course, your application will likely contain more complicated requirements, so it's important to understand whether these are addressed. 

Espresso Logic automates Advanced Examples with remarkable power, including
  • A Bill of Materials Price Rollup with 4 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 3 rules (how many bolts remain in stock after building n planes?)
  • An Allocation of a Payment to a Customer with 4 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, the Logic Engine is extensible, so you can utilize server-side Javascript, and even define your own rule types.

What does it take to get started?

You can be underway in minutes: create an account, create a project, and you are up.  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.

It is not required that you expose your entire database, nor rewrite existing logic.  You simply 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: