Did you and your team start embarking on a new project using the reactive approach and technologies, but are you in doubt as to whether you are doing things “the right way”? Let’s check right now how you are doing. With the Reactive Audit, I’ll take a look at your architecture and codebase, identify critical design and development anti-patterns and give you a set of recommendations as to how to best proceed going further.
Are you experiencing any of the following symptoms with your new reactive system?
- you were expecting stellar performance, but the system is way slower than you need it to be
- the development team can’t seem to agree on the best way to structure the code and to use the technology correctly, which doesn’t usually happen in projects
- the system was doing fine during development but now that you are performing load tests, unexpected behaviour starts appearing
You have done the necessary upfront evaluation, watched talks and read articles on the benefits of eventual consistency, non-blocking streams, the actor model and asynchronous programming and you know that this is the direction that suits your business best. While building the new application or after having launched it, you run into issues that seem to resist the usual problem-solving mechanisms your team is used to, and doubt as to what is going on slowly creeps in.
Your new reactive application needs an expert review
As a Reactive Systems consultant I have been helping technology companies for years to transition from the traditionally synchronous, database-centric model of thinking to the world of fully-asynchronous, non-blocking, event-oriented and eventually consistent distributed systems. I have written a book on the topic of reactive web applications, and more recently am putting together the experience gained from numerous consulting projects as a list of anti-patterns often found in client codebases (you can watch me talk about it).
With the Reactive Audit, you get the chance to hire me directly to have a look at your codebase. Here’s what I will do:
- check the architecture against the objectives of the system
- conduct a high-level code-review with a focus on the application of reactive principles
- identify critical design and development anti-patterns and lay out how to fix them
What will you get?
The key deliverable is a comprehensive, actionable evaluation of your application in the light of applying reactive principles, presented in the form of a PDF report. We will start by having a call in which you will tell me all about what your application is expected to do, how it fits in the bigger picture of the entire system landscape and what pain points it is supposed to address. After you give me access to your codebase, I will then proceed to analyze it following a process I have devised over the years. The report will consist of:
- an executive summary of how the application is doing in terms of applying the reactive principles
- a rundown of anti-patterns identified in the codebase, illustrated with specific code examples, an explanation of why this is problematic and how to address it
- an in-depth analysis of the various components of your application (for example, in the case of an Akka application, this would be a detailed analysis of the actor hierarchy)
What technologies do you audit?
I’m specialized in applications built with Akka and the Play Framework and Lagom, be it in Java or Scala.
Will I get a line-by-line code review of the entire codebase?
No. This audit is focusing on the application of reactive principles – asynchronous programming, reactive domain modelling, reactive application architecture – and is not meant to review a particular code style or proficiency in a language.
Will you audit my entire system comprised of 300 microservices?
Sorry, no. This audit is meant for applications that are in the beginning phase (you are just getting started with reactive applications and have a handful services) or for particular system that is part of a bigger landscape. We will clarify if your system is a fit at the very beginning of our conversation.
I don’t have much time. What do you expect from me?
Here’s what I need from you, which should not be costing you too much time:
- access to the codebase you want to have audited – this can be read-only access to a code repository or an archive of the source
- an hour (at most) of your time for a call in which I will gain an understanding of the objectives and surroundings of the application under review, both from a business perspective and from a technical perspective (it may be that there’s more people on your end involved in this call) stay in touch during the review, in case questions arise
- review the audit when it is done, circulate it in your team and ask clarifying questions which I’ll be happy to answer
How much will it cost?
- for prototypes, the audit costs 5950€
- for applications that are still under development and that have not yet been launched in production, the audit costs 9950€
- for the audit of production applications, the audit costs 14950€
I’ve always received very positive feedback when performing these audits. That’s why I provide a full 100% money-back guarantee on this offering. If you’re not happy with the audit results I’ll give you a full refund, no questions asked.
How fast will I get the audit?
In general you should count with 3 weeks to get the audit. If you need it faster / yesterday, we can talk about it.
I’m interested – how do we get started?
Please send me an email at [email protected] and briefly describe your business, the stage you are in with your application (prototype / development / production) as well as the main pain points you are encountering. If you’re a good fit for the audit, I’ll send you a link in order for us to schedule our initial consultation call.