Tech@Deriv - Deriv Tech blog

Tech@Deriv

Networking & Career Opportunities Await | HackerX 2023 | Deriv

Networking & Career Opportunities Await | HackerX 2023 | Deriv

Interested in joining the frontend or mobile development team? Attend HackerX 2023 and learn about open positions in these fields. Register today

Migrating To async/await (part 2)

Migrating To async/await (part 2)

Things to consider when rewriting code to use the new async/await syntax provided by Future::AsyncAwait. In part 1 we looked at how to rewrite code that previously used plain Future on its own for sequencing operations, into using the neater async/await syntax provided by Future::AsyncAwait. In

Migrating To async/await (part 1)

Migrating To async/await (part 1)

Things to consider when rewriting code to use the new async/await syntax provided by Future::AsyncAwait. The Future class provides basic asynchronous future functionality, and also a number of handy building-blocks for building larger code structures into meaningful programs. With the addition of the async/await syntax provided by

Awaiting The Future (part 2)

Awaiting The Future (part 2)

A further look at Future::AsyncAwait, where it will go next and how we should be using it. In the previous part, I introduced the Future::AsyncAwait module, which adds the async and await pair of keywords. These help us to write many forms of code that use futures for

Awaiting The Future (part 1)

Awaiting The Future (part 1)

Introduction At Binary, we have an increasing amount of code that uses Futures to represent asynchronous operations. The power of these objects comes with the increased complexity of writing readable code that makes use of them. Various articles I have previously written have described Futures and their use. In this

Unit Testing Asynchronous Code

Unit Testing Asynchronous Code

How writing asynchronous code using Futures can help simplify unit testing Well-tested code is always prefered over something that has no tests, as with more tests we can be more confident that the code actually does what we want it to. Within the realm of tests, there exists a spectrum

Future Caching Tricks

Future Caching Tricks

Caching the results of Future-returning functions Often when making read requests or queries to some external service, it is helpful to cache the results of these queries so that other requests for the same information can use that directly, rather than having to repeat the query to that same service.

Differential Memory Leak Analysis with Devel::MAT

Differential Memory Leak Analysis with Devel::MAT

A look at a slow memory growth case and how recently-added features in Devel::MAT version 0.38 can help get to the bottom of it. Slow Growth Over Time Given a process that grows a small amount of memory over time, it can sometimes be difficult to look for

One Thing At A Time

One Thing At A Time

Limiting Concurrency in Future-based Programming Sometimes a Future-based program needs to actively avoid concurrency in one specific way or area, and ensure that only one instance of a given operation is outstanding at any one time. While the program as a whole can make use of concurrency to do multiple

Tracing Perl memory leaks with Devel::MAT (part 2)

Tracing Perl memory leaks with Devel::MAT (part 2)

In the previous article, we took a first look at how to use Devel::MAT to help find the reason why a perl process kept using more and more memory. The cause last time was found to be a single string scalar that grew to a huge 1.6 GiB,

Tracing Perl memory leaks with Devel::MAT (part 1)

Tracing Perl memory leaks with Devel::MAT (part 1)

The Devel::MAT ecosystem allows developers of perl programs to inspect and analyse memory-related problems such as memory leaks, unexpected memory consumption, or odd state. So says the first paragraph of the user guide, on CPAN at Devel::MAT::UserGuide. The user guide then goes on a brief overview of