Espresso Logic Azure API Service

##Key Use Case for Cloud, Mobile Virtually all organizations are looking to leverage cloud / mobile technologies, to promote internal efficiency and external access. These require efficient networked data access to multiple databases, with enforcement of your business policy for logic and security.

Espresso creates Enterprise-class Azure RESTful APIs across multiple databases, enforcing your logic and security. It’s declarative, so it’s remarkably fast and simple to create systems as follows. See our webpage

Key Advantages of Espresso Logic API

Runs inside your Azure instance securely
Fully integrated into Visual Studio as an API Service
Support for multiple databases
Define custom resource endpoints (nested documents)
API created for tables, views, and stored procedures
Automatic pagination (forward and backward)
Optimistic locking
Role-based access to objects, column and row level security
Custom validation and business logic on multi-table transactions
Support for upsert (MERGE_INSERT)
Primary key propagation
Node.JS command line and web based admin portal
Dynamic (Live) view of data for back office testing
Swagger 2.0 Support
Support for large objects (Blob)
Simple REST API model

##Rapidly Create Enterprise-class RESTful Backends Create RESTful backends to accelerate delivering projects within your organization

Mobile apps: REST APIs are perfect for accessing multiple data sources. And Espresso dramatically simplifies your apps – rich nested document APIs providing filtering, pagination, optimistic locking, generated key handling, etc.
Integration: RESTful APIs define business objects that can be exchanged between systems
Partnering: create partner relationships by exposing selected APIs publicly
Modernization: break down monolithic web apps, by extracting their logic into a UI-independent microservices – API Apps that centralize data access with enforcement of logic and security. The resultant service can be shared across application architectures – not just heterogeneous web apps, but integration and partnering.

##Rapidly Publish Customizable API Apps to Azure API Apps to publish into the Azure catalog. Espresso handles the API, logic and security, Azure provides the marketplace, monitoring, and billing. Your business ideas get to market, fast.

Even better, logic can be customized by your customers – they just add rules, and the logic is automatically re-ordered and re-optimized. So not only do you get to market faster, your product is more flexible. ###The Difference is Declarative Espresso stands in stark contrast to “your code goes here” frameworks, by providing a declarative approach to creating APIs, integrating databases, and enforcing logic and security. You use a simple point and click interface to specify what you want, not the detailed coding of how to do it. The result is remarkable business value.

##Time to Market Declarative logic is 40 times more concise, since it handles all the details of change detection / propagation, SQL and transaction handling, etc. Technology automation means you can operate at the business level, delivering faster than you ever imagined.

The API is not just access, but also the enforcement logic and integration. Since this comprises a significant portion of a database oriented system, the savings in time and cost are remarkable.

The impact is not 10 or 15%. Our customers are routinely reporting getting a month of work done over a weekend.

##Faster Maintenance Cycles In procedural code, you spend most of your time deciphering existing code to figure out how to insert changes. And in monolithic systems, the change unit includes the UI.

Declarative services means that logic is automatically ordered, based on system-discovered dependencies. So you just change the logic. Eliminate the 3 month change cycles that drive sponsors crazy, and enable Continuous Deployment.

##Quality In procedural code, you not only have to ensure the logic exists, you have to analyze all the code paths to ensure its actually called. Ensuring compliance is a daunting task.

Declarative means you don’t call the logic – the system automatically invokes the proper rules on all incoming requests. If the rule is defined, it will be called.

It’s not just technical – Declarative helps you get the requirements right. Business Users can read the rules, and help spot errors. They can be engaged with the instant User Interface of Live Browser – much clearer than documents or diagrams. Unique Declarative API App Creation Declarative means you just declare what you want for an Enterprise-class API:

API: Default created instantly, then point and click Custom Resources with nesting and aliasing. Runtime support for filtering, pagination, optimistic locking, generated keys, etc.
Integrate: add new data sources, use in Custom Resources
Enforce: logic and security with spreadsheet-like Reactive Programming expressions, plus JavaScript based on an automatically created Object Model You also have deployment flexibility – Espresso operates on premise (VMware or Docker), or in the cloud (Azure or AWS).

##Create an enterprise API like this:

GET|POST|PUT|DELETE

/api/{table|view|resource}
/api/{table|view|resource}?{filter|arg.argname|sort|orderby|pagesize|offset}
/api/data/{table}
/api/data/{table}/{pkey}/{attribute}

Meta API (information about your service)

/api/@docs
/api/@rules
/api/@tables
/api/@tables/{tablename}
/api/@views
/api/@views/{view}
/api/@resources
/api/@resources/{ident}

tylerm007/AzureMarketService

Espresso Logic Azure API Service