Machine Learning (ML) dominates the narrative in financial services, just as in practically every other industry. In this piece we examine its current use cases and why the take up in Investment Management hasn’t been more widespread. We’ll then look at practical and achievable steps to harness relevant aspects of the innovation. 

Welcome back to FINBOURNE Five, our series of short ‘explainer’ blogs on all things data management, in five minutes or less. In this second installment, Sales Engineer, Stephen LeMasney, explores the critical factors to consider when looking for a SaaS data management platform, and why a cloud-native platform with innate financial sense is crucial to gaining immediate value and driving operational growth.

In this latest blog, Stephen LeMasney, Sales Engineer, shares his insights into how Python and Jupyter can be integrated within a 21st century data stack to drive efficiency and form a compelling tool for business users who want to learn new data skills.

This week we finally got to the bottom of a perplexing issue that we have been examining for a number of months now. We had been seeing intermittent HTTP timeouts or other unusual disconnection problems affecting LUSID, our investment data management platform. These were most obvious in our build pipeline, where they were causing test-failures.

Chris Brook, Co-founder and Head of Platform Engineering, FINBOURNE Technology, shares the limitations of the new tech trend ‘low-code, no-code’ as it applies to investment management operations.

This post is about Weave, our customisations, and a Weave related production issue that FINBOURNE encountered and resolved in the last couple of months.

Everyone knows that data is important, but do we really appreciate how important access to correct data is for the successful execution of an investment strategy?

Bitemporal data is a fundamental principle in our LUSID platform, yet the term is not very common amongst technologists nor business users. It can be a complex concept to describe, and I’ve been thinking of a simple example to help illustrate it…

Using nginx and oauth2_proxy to deliver S3 based content (and azure blob store)

Having spent the last 15 years cossetted in the big corporate world blissfully unaware of just how complex managing Identity and access control actually is, I can best describe my journey of the last month as enlightening. Emboldened by our mission and with the idea that we were, through the advent of cloud technologies, free from having to worry about such tedious things as user management, we embarked on our righteous path.

Azure currently has some pretty interesting rules and restrictions around how things can be named. At times they seem arbitrary, but none-the-less, it’s what we have to work with.