When you need to react quickly to competitive threats or new line of business demands, but your existing architecture is anything but nimble, what do you do?
Is it time to completely start over with a new enterprise architecture, or can you can augment your existing systems to become more resilient and responsive?
This slideshow features Michael Facemire, Principal Analyst at Forrester Research, and Kevin Webber, Enterprise Advocate at Typesafe, Inc., in a discussion about how to leverage a Reactive architectural model to ensure your back-end infrastructure isn’t the limiting factor for your business success.
27. Modernize with Proven Technology
Source: Typesafe
2
Conversions up 20%
Mobile orders up 98%
Achieved > 10x performance
improvement…on the same hardware
Reduced code base by 99%
from 479,000 to 5,000 lines
Improved elasticity to handle
100X increase in traffic
Modernized from monolith
to microservices
Radically simplified toolset and
architecture freed developers to
deliver rapid innovation
28. How they did it:
Typesafe Project Success Subscription (PSS)
• Full Lifecycle Support
• Access to our engineering team; Best practices
• Support Service Level Agreements (SLAs)
• Up to 1 hour 24/7 SLA
• Certified Build
• Validated integrations; Backwards compatible patches
• Training and Consulting
• Commercial Licensing Options
• Ongoing Knowledge Transfer
• Developer Recruitment and Speaking Opportunities
These are the four high-level challenges I am seeing from our clients regularly.
Build modern apps fast. Build your business faster.
Build modern apps fast. Build your business faster.
Build modern apps fast. Build your business faster.
Experience drives great mobile apps, but where is the experience created? While most focus on the front-end, in reality there are performance impacts all the way through the stack. Running a DB index at an inopportune time can create a delay that was never expected by front-end devs.
Initial quality is important – due to app store curation
Expedited releases are no substitute for real testing
“Blue/Green” environments complement A/B testing approach
Deployment and feedback management tools grow in importance
Simultaneous release across clients is important
Avoid patches – bundle bugfixes with new features
Don’t wait for GA – use platform betas
Moves to organic releases that meet user and market demands
Unfortunately this isn’t a panacea, there will be new challenges that come with the new opportunities this stack affords. Keep these in mind as you move forward:
-- API design is as much art as it is engineering. You’ll fail early, ensure you learn from each of these.
-- APIs aren’t a single layer, they’re more of a choreography of multiple API tiers. Ensure that this choreography maintains performance standards.
-- Injection of role-based access, business intelligence, and analytics increase the striation.
-- Service security, metering, commerce, and analytics are all handled in this layer.
-- There’s a LOT going on, so a focus on “transactional” performance is critical.
Yesterday’s model does not scale and performance breaks down under load
Yesterday’s model does not scale and performance breaks down under load
Yesterday’s model does not scale and performance breaks down under load