November 26, 2016
At Incapture we often implement data ingestion workflows for clients, typically as part of a larger re-engineering effort. Frequently, this involves waiting for and loading file-based data to arrive from another system or vendor. This is where Java’s Watch Service comes into play. Recently I was reading about Java’s Watch Service
, which is included with the java.nio.file package
, and thought this would could help us with client engagements.
Watch Service allows you to monitor directories and what types of events you want notifications for. Events are create, modify and delete; more details here
We have released 'WatchServer
' as part of our open source platform. The server provides a file system monitoring capability that maps file system events to Rapture actions in a repeatable and configurable fashion.
Typically the action would be a Workflow. As a reminder ‘Workflows’ in Rapture:
- Are constructs that define a set of tasks (or steps) that need to be performed in s...
September 6, 2016
At Incapture we implemented a REST server to demonstrate exposing Rapture (Kernel) calls through a REST style interface. Specifically, to perform CRUD operations on the various Rapture data types: document, blob and series. This approach can be used when modeling and implementing your own Rapture client's domain resources and interactions.
We wanted to use a simple and straightforward REST framework so we choose http://sparkjava.com/
. This allows you to get started quickly and provides everything needed to build an API.
Lets focus on Rapture ‘Documents'. One of the prime uses of Rapture is to manage access to data. Rapture has the concept of a repository for managing access to data. Various repositories, configurations and implementations are provided 'out of the box'. For the purposes of this post we will be considering a versioned document repository hosted on MongoDB.
Document data repositories manage data as key/value pairs and are addressable through URIs. In fact, all...
July 21, 2016
San Francisco and New York City - July 14, 2016
Incapture Technologies (“Incapture”) sponsored a gathering of leading practitioners to explore how asset managers can harness new data sources, analytical tools, and technology platforms to drive performance in coming years. Organized and hosted by United Sales and Marketing Group (“USAM”), the event was held on July 14th at the Core Club in New York City.
The event featured a panel discussion moderated by Peter Knez, co-founder of Incapture. Peter enumerated the factors which have created conditions for profound disruption in asset management and highlighted why embracing "datafication" is essential for firms to gain and maintain an edge going forward.
Drew Kellerman, Managing Director of Business Development for Vertical Knowledge (“VK”), shared examples of how open source data can be curated to generate actionable insights that inform investment and trading decisions.
Braxton McKee, Founder and CEO of Ufora, highlighted ...
June 21, 2016
Building from an earlier blog post
which provides conceptual grounding on entitlements, this post provides some practical examples of how to implement entitlements in Rapture.
Entitlements in Rapture allow administrators to clearly define who can access what in Rapture. It is a permissioning system based on users, groups, and entitlements. API calls made to Rapture are protected by entitlements that are defined at compile-time. A defined entitlement is associated with a number of groups of users, and this association can be made at run-time.
- A user represents a person who is making calls to Rapture or an application that is making calls to Rapture. A user is a single entity with a username/password who needs access to Rapture.
- A group represents a collection of users.
- An entitlement is a named permission that has associated with it 0 or more groups. If an entitlement has no groups associated with it, it is essential...
June 8, 2016
Clients building applications using Rapture may want to collect payment from users based on some usage metric (recurring subscription, service-based fees, consumption-based fees, etc.). In this blog post, we will describe how we integrated Stripe
with Rapture to set up a subscription service for our hosted trial environments through the Incapture developer portal
Stripe offers a suite of APIs that support online commerce. Two aspects of their offering stood out to us -
i. Emphasis on security and PCI compliance
-- all sensitive credit card data is directly sent to Stripe’s vault, without it touching Incapture’s servers
ii. Developer-friendly APIs -- good documentation wins, hands down.
I’ll give examples of how easy it was to build the integration using Rapture’s Reflex language -- a procedural language that runs on the Java Virtual Machine -- with Stripe’s API. This article is as much about Stripe subscriptions as it is about Rapture, Reflex and a front-end framework (in...