SlashDB is presented in context of systems of engagement. We discuss how to construct a uniform data architecture spanning enterprise and web.

Enterprise CIOs employ /db’s resource-oriented architecture to overcome data silos and shorten time to market for new business processes. Mobile enterprise application developers save time with /db used as gateway to legacy databases and can focus on engaging and value-adding business features.

Our founder and chief architect of SlashDB, Victor Olex was quoted about challenges with integrating traditional databases and web-scale information systems.

Here’s the link to the article:

http://techcrunch.com/2013/05/05/6-experts-on-speeding-up-data/

Enjoy.

Technocrati code 8VT4WUYJAVCM.

SlashDB seamlessly connects databases to authorized web, mobile and enterprise applications so that database content can be accessed in a uniform way from just about anywhere. The product has applications in master data management, data virtualization, data publishing APIs and mobile enterprise apps among others.

The New York Enterprise Tech Meetup is a monthly forum where innovation-seeking executives and venture investors meet cutting edge technology firms to freely network and learn from each other. Every month a select group of enterprise technology firms is asked to present at the event.

SlashDB is pleased to be a technology partner to the event among esteemed financial and web technology businesses such as: 10gen, Bloomberg, Caplin, CardFlight, Disqus, Dwolla, Estimize, Kaazing, Oanda, OpenFin, OpenGamma, StockTwits, Tradable, Xignite and Zipmark. Special thanks to Nick Gavronsky from OpenFin for inviting us to participate.

Although SlashDB has grown to become an industry agnostic database-to-web “middleware” the idea for it was actually conceived out of problems with data management observed in large financial institutions.

As you may know, SlashDB can create a mesh of all your database resources accessible in the same way, by referencing URLs. We call that a Resource Oriented Architecture (ROA). With the ROA approach there is far less of a need to use ETL processes and data warehouses. Instead of copying data, use a reference to data.

Data transparency and a capability for instant error correction naturally stem from this approach. Also, the fact you can use the same link to power an in-house trade processing service or a risk dashboard on a mobile device or even desk quant’s Excel workbook is for some just too good to be true. Except it is true and will become a norm.

SlashDB instance running on Amazon Elastic Cloud will be made available to the hackathon participants and will support any Amazon RDS databases (SQL Server, MySQL, Oracle) as well as SQLite files. If you have any questions for us ahead of the event, please send them to finhack @ slashdb.com.

We hope to see you there! Don’t delay, register now.

Here’s what’s new in 0.7:

For data scientists, business analysts

SlashDB has this dual personality. It is the API developer’s best tool to incorporate databases into his/her web or mobile apps but the equally important aspect of the system addresses the needs of data scientists, business analysts and rapid application developers.  Using SlashDB they get straightforward access to relevant data in its unobstructed form. Thanks to our latest GUI enhancements the web interface is now even more user friendly. New, responsive design allows for comfortable browsing through data on mobile devices while automatically generated, drill-down, filtering and sorting links help casual user discover the data and system’s functionality on the fly. As before you can use your favorite data analysis tools such as Excel, Matlab, SAS, R etc. to work with live data referenced by /db URLs.

For system administrators

Previously most settings would require editing configuration files on the server. We still have that option but since version 0.7 nearly all settings can be made in the web GUI or via a REST API. New authorization schemes now allow even greater flexibility in creating user segments with distinct permissions to data and system functions. Special users “admin” and “public” have been added. The former has full permissions to all system functions. The latter can be configured to offer limited access without requiring a login.

For CTO/CIO and software architects

Using SlashDB as a mobile enterprise application backend or to build an API is a sensible choice. Not only can you instantly leverage prior investments in databases but also remain in full control of your solution. That is because unlike SaaS offerings SlashDB can work in your data center or in your private cloud. See also this blog post.

User Experience in ver. 0.7

It all changes with SlashDB.

Once installed next to a web server, SlashDB connects internal databases to authorized mobile and web applications. Technically speaking, it automatically constructs a REST/HTTP web service, which makes database content accessible by URLs for reading and writing, under compatible data formats.

Using SlashDB, enterprises can create meaningful systems of engagements themselves or in partnerships with clients or 3rd party developers.

SlashDB as a Data Gateway (click to enlarge)

The benefits of HTTP APIs go beyond just modernizing the technology infrastructure and translate to competitive advantage for one’s business.

For example, an executive could negotiate a better deal by having an up to date inventory data on hand. The inventory itself could be accurately calculated because purchase orders were captured on the fly from distributor’s outside salesperson’s device into company’s database.

Systems or engagement are about interaction, in the moment updates and sharing but they make business sense only if they can work with and leverage prior investments made into the systems of record. SlashDB makes the connection.

“Data API as a Foundation for Systems of Engagement”

Enterprise evolution to systems of engagement will only succeed if it can leverage and add value to existing systems of record. Relational databases are predominantly used for that but their content can be rather difficult to engage with. This holds true not only for the non-technical staff but increasingly also for the new breed of software developers, who are accustomed to the pragmatism of web APIs.

We are introducing the idea of Resource Oriented Architecture as a foundation for building enterprise systems of engagement. ROA is a data abstraction layer (API), which uses URLs as references to the data at source (database). We will show a functioning implementation of ROA in SlashDB and discuss both internal and external applications for this approach in a modern enterprise.

SQL database servers are designed for fast and reliable local area networks where constant connection between client and server can be maintained. VPN tunnels often shut down when there is no traffic, which can break existing connections. Further, the performance leaves a lot to be desired due to encryption and other overheads. People complain – a Google search for “database over VPN problem” yields almost 8.5 million references.

When database content needs to be accessed by remote clients over the Internet, an HTTP(S) web service is most likely the best solution. HTTP was designed for wide area networks and automatically comes with benefits of efficient caching, easy content sharing and is accessible from virtually all programming environments.

Data from SlashDB shown in KendoUI app.

There are two code parts that make up the app.

1. Declarative HTML5 application layout

<!--Add Mobile App HTML --></pre>
<div data-role="view">
<div data-role="header">
<div data-role="navbar">Northwind Customers</div>
</div>
</div>
<pre>

2. JavaScript initialization and data fetch code

//Mobile App Initialization Code
var ds = new kendo.data.DataSource({
    transport: {
       read: {
            url: "http://demo.slashdb.com/db/Northwind/Customer/CompanyName.json?limit=41",
            dataType: "json"
        }
    },
});

ds.read();
window.ds = ds;
var app = new kendo.mobile.Application(document.body);