Creating APIs‎ > ‎Database Creation‎ > ‎

Managed Data Background

SQL is a great language.
For computers, not people.

Bob Epstein, founder, Sybase


This page explains how you can create a new database from a simple business-oriented metaphor, consisting of only master/detail and lookupsThis page provides some background on intended users, and their setup considerations.

For more information about connecting to an existing database, see Database Connectivity.

 

Database Creation Challenges

The following diagram illustrates the following flows for creating a database:

  • Existing database. The upper flow begins with an existing database.
  • New database. The lower flow begins with a new database (or new tables in an existing database).


In both flows, the schema creates a default API, which your team can customize, define reactive logic, and create client applications. The lower flow (new database) illustrates the following common challenges in creating databases:

  • Creating data servers. This is challenging even for experienced application engineers. The administration obstacles alone are formidable.
  • Database coding. After you create the database, you must code the schema using SQL syntax, possibly with common database tools. You would prefer to spend time developing rather than fighting with SQL syntax. For business users, it is a blocker, requiring mastery of not only SQL syntax, but also the complex concepts behind it, such as normalization and foreign keys.

The diagram suggests that accelerating and simplifying these steps can further reduce the time of bringing new ideas to market. And, just as important, if you can eliminate the complexities of schema syntax and concepts, a new class of people are empowered: business users.

User Personnas

In planning for managed data, consider the following user personas:

For  Value
Developers
  • Eliminate delay in server creation.
  • Reduce tedious SQL syntax.
  • Retain extensibility and customization.
Business users
  • Create applications from the following simple familiar visual metaphors:
    • Master/Detail
    • Lookup
  • Business logic by way of spreadsheet-like reactive logic.
Managers
  • Deliver projects much faster.
  • Empower business users to create their own systems.
Architects
  • Systems created by business users are supportable.
    • Run on standard servers.
    • Business logic for integrity.
    • Scalable performance.
    • Pre-integrated, with automatic RESTful APIs.
    • Extensible, with standards-based metaphors and languages.

Set up for Managed Data

Whether you are serving a community of developers, business users, or both, complete the following initial setup steps:

  1. Create a managed data server.
  2. Authorize users to create managed databases within the managed data server.
For more information about how to create a managed data server and how to authorize users to create a managed database within the managed data server, see Managed Server Administration.

Enterprise Class

As suggested from the previous API Creator Work Flow diagram, creating new databases, and their APIs, using API Creator is an alternative starting point for API creation. You still get the enterprise-class services for scalability and reactive logic, with an interoperable API to support mobile apps, systems/partner integration, and heterogeneous client development.

The starting point for API creation is mix and match. You can perform the iteration cycle using Data Explorer and/or your existing database tools. Business users can develop initial prototypes and then execute them as departmental systems or integrate them into the larger systems by IT.

More Information

For more information about managed databases, see Managed Data Servers.