After deciding last year to take a step away from doing StreamBase consulting, a very interesting opportunity to take on some greenfield projects for a technically sophisticated FX quants desk to address shortcomings in their current trading platform.
This is my first exposure to FX, and for someone more familiar with equities it’s quite an eye-opener. For a technology person, it’s exciting to have the chance to design and build systems that are up for weeks at a time instead of from 07:00-17:30 5 days per week.
Another part of my new role involves training a group of 5 experienced developers who are new to StreamBase, which has been a great experience. There is nothing like questions from a bunch of experienced professionals to push one’s own understanding deeper, and to sharpen up the details of some previously fuzzy ideas.
I am participating in a webinar hosted by StreamBase where I’ll be discussing the integration of Java and StreamBase on different types of projects. I hope you will find it an interesting discussion of how to strike a balance between StreamBase and Java in your projects, as well as some of the different ways to integrate the different programming environments.
If you’re interested, you can sign up here.
Lately I’ve had a few people wanting to discuss their proof of concept and/or vendor & tech evaluation projects with me, specifically around evaluating StreamBase for their needs on upcoming projects and products. Seems like as good a topic as any for an article, so here we go. My first use of StreamBase was when I was driving a PoC project for my then-employer, so I feel like I have some insight to offer on the subject, based on that and on my years of experience since.
There are 4 broad categories to consider when planning and executing any project like this: effort and duration of the PoC, project definition and scope, choosing the right resources, and applying the correct evaluation criteria. This article will offer some guidelines and suggestions for those 4 categories, specifically as they apply to evaluating StreamBase for your organization or project.
The following quote is often misattributed to Abraham Lincoln:
Give me six hours to chop down a tree, and I will spend the first four hours sharpening the axe.
My bit of research hasn’t been able to identify the correct source of this remark, but regardless of who said it, I think it contains some valuable wisdom that is directly applicable to the development of software systems, large and small. In this article, I share some thoughts about being properly equipped and prepared to develop software in a professional setting.
I am participating in a roundtable discussion hosted by StreamBase. There are 2 other panelists, both part of in-house development and architecture groups at capital markets companies. I believe it will be a lively and enjoyable discussion about some of the ins and outs of adopting StreamBase CEP technology.
If you’re interested, you can sign up here.
The recorded call is now available online. You can watch it here if you’re interested. The content covered in this call is primarily about adopting and ramping up on StreamBase.
Lately this blog has been a bit less active than I would like in terms of new content. The reason is because my off-hours work these days has been going into completing the programming assignment for the StreamBase Certified Developer program.
I haven’t finished it yet to earn my certification, but I thought I’d share a bit about my experiences so far in a quick post. Once I’m finished with it and am certified, I’ll return to my regular posting on a broader range of topics, and documenting some forthcoming SBX additions.
I held off on doing the SCD program when it was initially announced as I was already relatively experienced with SB and familiar with the material covered in the course that it relates to. Add to that, I had a stable contract with a big customer to do SB development. More recently, I decided to go ahead and invest the time for the following reasons:
Read the rest of this entry »
The StreamBase development platform is marketed on a number of selling points, the two main benefits being high performance and rapid application development (two benefits that are generally presumed to be in opposition with one another). In this article I will share my experiences positive and negative regarding the productivity of working with the StreamBase platform.
The discussion touches on EventFlow coding vs. the Java and .Net platforms, the value of the library of adapters, and build/test/deploy realities.