Stephen Darlington

← GridGain Blog

Stephen Darlington
Position:
Training and Consulting Services Manager
Bio:

Stephen is the Training and Consulting Services Manager at GridGain, where he helps clients meet their business goals using unified real-time data and in-memory technologies. 

He's worked with high-performance, data-intensive applications for over 15 years and has experience across many industries, including telecoms and financial services. 

Also, he is an active Apache Ignite Committer and top non-code contributor helping Ignite developers on the user list and StackOverflow.

Bio:

Stephen is the Training and Consulting Services Manager at GridGain, where he helps clients meet their business goals using unified real-time data and in-memory technologies. 

He's worked with high-performance, data-intensive applications for over 15 years and has experience across many industries, including telecoms and financial services. 

Also, he is an active Apache Ignite Committer and top non-code contributor helping Ignite developers on the user list and StackOverflow.

It’s an exciting time in the world of trading. After a long period where transactions would typically settle in two days, we’re rapidly moving to same-day settlement and, in some financial markets, instantaneous settlement. In the capital markets jargon, this is known as T+0.But what is “settlement”, why is this important, and how does reducing the time to settle affect your organization?What is…
Some databases have a feature where a column can be “auto-incremented.” In this piece, we’ll explain why GridGain and Apache Ignite do not, and what you can do to get equivalent functionality. The naming varies, but the concept is straightforward: the system automatically generates a key for you if there is no unique business key for a table. Typically, this would be a numeric column, and…
Every industry is experiencing massive increases in the volume of data, the number of queries, and the complexity of requests. At the same time, requirements for low latency are also increasing to keep up with the speed of business. This trend has been apparent in capital markets perhaps longer than in other industries due to intense competition and a willingness to be early adopters of…
To improve application and query performance, developers frequently use summary tables. The summary table pattern is where we feed data into an Apache Ignite or GridGain cluster into two tables: the original data; and a summary, or rollup, of that data. With GridGain’s SQL engine, it’s not always necessary to have a summary table! For many, perhaps most, use cases, the fact that the data is…
In-memory computing can provide tremendous benefits for the 5G ecosystem. We’ve seen the marketing for the fifth-generation mobile networks. The benefits of 5G for end-users are easy to understand. Speeds faster than your home broadband and latencies only a little slower promise to be game-changers for consumers, enhancing existing applications and opening open entirely new categories that we…
Overview Prometheus is a popular monitoring tool that is supported by the Cloud Native Computing Foundation, the group who support Kubernetes. We often see Apache Ignite and GridGain users trying to integrate Prometheus with their clusters. This post provides hints about how to integrate Prometheus with Apache Ignite and GridGain. Prometheus Configuration This post isn’t about how best to…
Where do you store your passwords? Whether you’re integrating Apache Ignite with a relational database, a message queue, or something else, you probably need to manage secrets such as usernames, passwords, and security tokens. In this post, we consider a couple of options to avoid having secrets in your configuration file: using property files and integrating with HashiCorp Vault.…