At YoppWorks, if there’s something we’ve always been excited about, it’s staying on top of new technologies and adopting change in the open source market. As we’ve gone through our journey, we’ve been exposed to the vast dynamics of running a software-driven company. As a part of our own business model and how we offer solutions, we often bridge the gaps and challenges that our customers face on a day to day basis.
One of the major challenges that we’ve seen our customers overcome is deciding how to navigate the reactive world. Like our partners at Lightbend, YoppWorks help customers introduce themselves to modern software development practices through our consulting, training and solutions. Lightbend, is a pioneer in this paradigm shift and provides insightful guidance that enterprises need in this reactive world. At YoppWorks, we know that organizations want to adopt reactive platforms and get very excited about microservice architectures, but often don’t know where or how to get started. This is where Reactive ATI comes in.
What is Reactive ATI?
YoppWorks in partnership with Lightbend has developed a productized service offering that consists of three very important phases:
Phase 1: Assessment
Phase 2: Training
Phase 3: Implementation
YoppWorks Reactive ATI is designed to be a concise and repeatable methodology that provides very specific deliverables to our customers. Reactive ATI provides guidance and the type of information needed to further important decisions in reactive architecture practices. Reactive ATI is also designed for enterprises that have already tried to deploy reactive architecture in the past, but who haven’t achieved the benefits that they expected.
No matter the scale of your company, when approaching reactive solutions, it’s essential for contributors to see and understand how they would design and build something that has a clear ROI (Return on Investment).
“It takes time to succeed because success is merely the
natural reward for taking time to do anything well.” – Joseph Ross
Throughout numerous customer engagements, we’ve found that companies are at different points of maturity to adopt a reactive architecture. As opposed to the traditional mindset of “let’s start and deploy!”, Reactive ATI recognizes that organizations need time to discuss where to best deploy this architecture. In evaluating any new technology, it’s really important to have a strong starting point. Reactive ATI offers three key Deployment Phases:
Design > Build > Run
In order to get into these phases properly, having a real understanding and roadmap of what it is that you’re trying to accomplish is critical. Most importantly, Mike Kelland (VP of Services at Lightbend) notes that “Reactive ATI enables Lightbend customers to kickstart their journey and build a roadmap for success”.
What is the Lightbend Maturity Model?
The Lightbend Maturity Model is designed to be an in-depth look at the adoption of new technologies throughout the transformation process. As Mike Kelland explains, certain organizations in the industry are known as digital natives.
These organizations tend to have digital transformation as part of their DNA. This simply means that companies like this are built on the idea that they have to continuously disrupt themselves. Digital natives that share this methodology would be companies like Twitter, Google, and LinkedIn. These are the kinds of companies that have the ability to quickly implement new technologies in an ever-changing ecosystem and get them out the door.
If you’ve been paying attention to trends in the digital landscape, this is where technology and software is going. Mike notes that “We’re moving to this world where everyone has to be a software first company. In the Lightbend Maturity Model, we set you up with the difference between what you’re doing today and what a digital native is doing.”
With the Maturity Model and Reactive ATI, we can understand how willing your organization is to adopt new ideas and what that roadmap would look like. From here, Mike Kelland goes on to mention that Lightbend comes up with a Maturity Model using their own stack. This helps to place your organization on that scale: from traditional business (where software isn’t the main focus) all the way to Digital Native. See general maturity model scale below:
Traditional Business > Expanding Stage > Standardizing Stage > Digital Native Stage
It’s important to note that where you are in terms of your organization’s maturity makes a big difference in how you should try and adopt these technologies. It’s also important to note that you’re not going to jump from a Traditional Business to a Digital Native without properly pulling the right levers to get there. Reactive ATI determines what the key levers are to pull yourself up effectively on this scale. We’re dedicated to determining what it is that is going to enable your enterprise to become highly successful.
The Assessment Phase is designed to be an on-site engagement where we would send a YoppWorks architect directly to a customer’s location to coordinate with the sponsor. During this engagement, our architect will spend time with various stakeholders as well as the development team to gather their insight and better understand the current development process.
During this phase, our interests specifically surround architectural tooling and current deployment practices while simultaneously providing a holistic examination of your software practice. This includes Team Structure, Planning and Design, Development, Release, Architecture, Tooling, Code and all of the details in between.
Where is the value in Reactive ATI?
The business value is all about driving your project. In order to achieve business value with software, Mike Kelland points out that you need to be responsive. This means that no matter or what, it’s essential to respond to a user or a client. “These systems need to scale up and scale down. If there’s a loss or a failure in any component of the system, we maintain that responsiveness and continue to deliver the business value.”
The only way to a achieve elastic and resilient systems is through a message-driven architecture. If you don’t have a well-designed message-driven architecture in the background, we can’t hope to achieve true elasticity or true resiliency. Therefore we lose our responsiveness and lose true business value. As Mike puts it, “this is why Reactive ATI makes sense.”
For the second phase of Reactive ATI, we engage in Training. During this phase, the same YoppWorks architect(s) will then work with you the following week to do an onsite training engagement. As Jack Gulas, YoppWorks CEO explains “What’s really cool about this course and why it aligns to Reactive ATI offering is that it’s not just a technical course, it’s a holistic approach to reactive architecture.” Part of this approach is that students will design a reactive application with the YoppWorks architect(s) and would analyze a sample domain. Once complete, the organization would compare this to how they traditionally build monoliths. Another cool feature about the training component is that Reactive ATI takes the time to go over the overall benefits of this new architecture from at a business level as well as a technical one.
At the very least, it’s clear that Jack and Mike are extremely excited to stand behind a training course that plugs a real hole in the industry. Something that moves away from the traditional use of data. Today, there is a shift in the interest of streaming the contextual use of data. The industry demands the understanding of microservice based environments that are highly agile and flexible, able to be changed. This is what Reactive ATI can offer.
During Implementation (which will consist of approximately 1 week’s worth of effort), our YoppWorks architect will guide the steps for rolling out a reactive architecture. This phase has the flexibility of being done on-site or remotely. During this phase, we will also teach you how to maximize the benefits of the technology components within your report. This will help you leverage the steps and recommendations as to where to start within your own capacity.
Implementation is designed to be an efficient and repeatable step. During this phase, it is up to each enterprise to decide which levers they want to pull to begin the transition of their own reactive architecture. YoppWorks architects will be available during each step of this phase to ensure smooth transitioning and maximum benefit.
“You owe it to yourself to take a deep look at this Reactive ATI process just so you can come up with an assessment of whether or not this is going to fit into your environment.” – Mike Kelland, Lightbend’s VP of Services
Beyond the tech and all the buzz, how does Reactive ATI help my business?
To bring Reactive ATI into a comparison of real-life use cases we will bring your attention to a particular use case as discussed at the Reactive Summit in Austin Texas this past September. (For confidentiality purposes, we will refer to this large company as “Company X”)
In this use case “Company X” was able to demonstrate the reward that can be given when you properly plug your business into the world of modern software development of Lightbend technologies. Some would argue that they broke the model in this particular case. “Company X'”s goal was to increase the number of people who bought things off of their website. They were able to build a well thought out reactive system that was very snappy, message-driven and reactive with this massive load. This implementation lead to 1.6x more conversions on the website. In other words, they had a 197% increase in sales. The most incredible part of this use case was that they were able to save over 4000 hours of development time during implementation.
As Mike Kelland puts it, “This is why we call this a bit of a software revolution.” The way that “Company X” was able to evaluate a technology and approach had a direct impact on their conversions. They gave it a shot and the benefits that flowed from that were exponential. From a technological standpoint, they had incredible agility in their model and to do this, they created a clear and concise starting point. This is the type of inspiration that we are using to build Reactive ATI. Beyond the technology, this is where the true value lies.
How do I know that Reactive ATI is a true Reactive Solution?
In short, it’s no surprise that the Reactive terminology is something that Lightbend pioneered. But if we take a step back in time 2 or 3 years ago, this wasn’t a term that was used very often. Today, it’s everywhere. Even wider than that, we’re now in a world where there is a massive consolidation of data in the cloud and a need to serve massive amounts of people. What we’re seeing now is that everyone is calling themselves “Reactive”.
One of the challenges with this is that there are people who do truly have strong implementation and others who are just jumping on the bandwagon. To determine true validity, when looking at these Reactive Solutions, these solutions have to be message driven. This is the core of reactive systems and how it ensures that you’re building something elastic and resilient.
“This creates the ability to build a system that doesn’t have any kind of blocking or tight integration between various different components. So if you’re making a method call, or a rest call or other ways to communicate between systems, ensuring that system is not relying between its components on the delivery of a message or on the resolution of a call and you can truly build a system that is asynchronous and that each component of the system is isolated in the system in a way that it can operate independently. Without that kind of architectural outline, you can’t fulfill all the tenants of the reactive manifesto and you’re not going to get all those benefits.” – Mike Kelland, Lightbend
Going through Reactive ATI, allows you to deeply understand this and will help you to evaluate how those solutions are going to benefit your environment.
Let’s get Reactive!
Contact our Sales Director Adam Peck at firstname.lastname@example.org for your free Consultation!
Content sourced from: Jack Gulas, Mike Kelland (webinar: https://www.youtube.com/watch?v=hdNGH44wi34)