open-source

ServiceMerchant – Ruby toolkit for recurring billing and subscription management 1

ServiceMerchant is an open source library for Software-as-a-Service applications, based on subscription payments and various service plans. It’s available under MIT license for more then a year. It’s home page is here.

The library consists of number of well-isolated and well-defined components, so that you may re-use portions of the library, should you find the full functionality not required for you. If you choose to use the library as whole, it should cover most of your payments requirements, thus being billing module for your application.

ServiceMerchant’s main purpose is providing gateway-independent support for recurring billing operations and powerful high-level tools for building subscription-based billing atop of it. It is built on top of well-known Active Merchant library.

ServiceMerchant can be used both as a Rails plug-in or standalone Ruby library. It is also possible to integrate ServiceMerchant with non-Ruby web applications via REST interface or common GUI.

Supported Gateways: Currently Authorize.Net and Paypal Website Payments Pro (US) are supported.

Generally, if Active Merchant supports some gateway with recurring billing features then it is easy to add ServiceMerhant support as well. In this case you’ll only need to add a few lines of proxy code between Active Merchant and common recurring billing API.

How do I get it?

git clone git://github.com/itteco/service_merchant.git

If you’re not using git, you can download snapshot from Service Merchant page on github.com

Components

ServiceMerchant consists of three relatively independent components:

  • Recurring Billing API – is aimed at providing uniform interface for recurring billing features of payment gateways and making switching from one to another as painless as possible.
  • Transaction Tracker – stores local and readily available snapshots of so-called “recurring billing profiles”. With Tracker you can check account status much faster than vie gateway query (which not every gateway API includes). Transaction Tracker hooks automatically to Recurring Billing API and updates your local copy of data according to all ongoing operations.
  • Subscription Manager – provides high-level logic for managing subscription services, tariff plans, payment policies and so on. You can even use it to automatically adjust final price with the tax of appropriate region!

Give it a whirl on your next SaaS project, Ruby or other. We have successfully integrated ServiceMerchant into Python/Django application, for example.

jFuSea – Java based Fuzzy search library

Back in May 2009 we open-sourced jFuSea – Java library, which allows implementing fuzzy logic searches based on pre-configured settings.

It got the following features so far:

  • Initial linguistic analysis (lexeme and morphologic) of user’s request. It allows clean request from stop-words and determine part of speech for all words of request and also to construct all word forms to search. The results are returned as XML-documents, making it easy to put it in a database with request builder.
  • Preparing your database by making word-based index tables for some document table. In general cases you may configure only library’s text files without code modifications.
  • API for searching indexed documents using configurable SQL-queries. Request builder to translate results of linguistic analysis into a database query.
  • Samples of usage: Craigslist aggregator and search of recent advertisements to search above cities and categories.
  • Web demo-application for demonstrating search for Craigslist advertisement database.

Check it out at Google code.

Big Table Solution

Big Table Solution (BTS) is Apache 2.0 – licensed open source Java library, we published back in April 2009.
BTS is essentially a JDBC driver which allows applications to operate with distributed multiple database instances as they do with the single database. It offers a solution to the problems that arise with the growth of the volumes of data in an application’s relational database and parallel growth of load on the database layer.

Relational database management systems would typically provide partitioning and/or clustering to deal with those issues. BTS, for one, offers an alternative solution by suggesting to split application’s data into more than one database instances and taking the responsibility of executing particular SQL queries against the relevant database instances.

Since BTS resides between application’s data access objects layer and JDBC drivers of the database being used, it can work with any RDBMS that goes with a JDBC driver.
BTS itself is implementation of JDBC driver specifications, making it easy for developers to integrate with. It may also be used with either plain JDBC or with literally any persistence framework (e.g. Hibernate or iBATIS).

Visit library’s homepage for more details.