Remove Architecture Remove Best Practices Remove Software Architecture Remove Strategy
article thumbnail

10 talks to look for at the 2018 O'Reilly Software Architecture Conference in London

O'Reilly Software

From chaos architecture to event streaming to leading teams, the O'Reilly Software Architecture Conference offers a unique depth and breadth of content. We received more than 200 abstracts for talks for the 2018 O'Reilly Software Architecture Conference in London—on both expected and surprising topics.

article thumbnail

Up your quality and agility factor – using automation to build “performance-as-a-self-service”

Dynatrace

This involves new software delivery models, adapting to complex software architectures, and embracing automation for analysis and testing. One way to apply improvements is transforming the way application performance engineering and testing is done. Performance-as-a-self-service .

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Explore Autonomous Cloud Management at an Autonomous Cloud Lab

Dynatrace

You’ll be introduced to modern software architecture concepts, containers, feature flags, CI/CD pipeline tools, container orchestration tools, runbook automation tools and much more. Following on from that, our developing microservices lab session will demonstrate best practices you can leverage for microservice development.

Cloud 134
article thumbnail

The ‘Chocolate Sauce’ Design Heuristic

Strategic Tech

And there is no single best practice. A Software Example Consider the example of a marketplace for financial products. And of course, when you need to choose the most suitable design, The 5 Primary Heuristics of Sociotechnical Architecture will help you to identify the optimal solution for your business needs.

Design 40
article thumbnail

Mapper Contexts & Supercontexts: Decoupling Domain-Specific and Domain-Generic Bounded Contexts

Strategic Tech

You’re building a new system and two members of your team propose alternative architectures for sending notifications. How will you design the most effective architecture which supports short-term goals and long-term evolution? So Commands from Specific to Generic is a Best Practice? Which one is correct?