Presentation: Design Microservice Architectures the Right Way
Share this on:
This presentation is now available to view on InfoQ.com
Watch videoWhat You’ll Learn
- Understand from first-hand experience the many critical decisions you make in designing your microservice architecture.
- Learn first hand what decisions are critical; and which will lead to paralyzing technical debt over time.
- Hear a step by step use case of building a successful microservice platform with all the critical points along the way.
Abstract
Learn from first hand, deep experience, the most critical decisions we face in building successful microservice architectures: how to think about the tradeoffs that impact the productivity of our teams and the quality of our software. In particular, understand how to avoid creating an architecture that eventually (and sometimes quickly) paralyzes our ability to execute. This talk highlights specific key decisions that very directly impact the quality and maintainability of a micro service architecture, covering infrastructure, continuous deployment, communication, event streaming, language choice and more, all to ensure that our teams and systems remain productive as we scale.
Can you give us a teaser of what to expect in this talk?
We will go step by step and talk about the investment needed to run a successful microservice platform, touching on everything from contracts, events, data structure, shared libraries, deployment, isolation, monitoring, etc.
Our primary thesis is to reinforce that a microservice architecture requires significant investment (as do all architectures) to be successful - and then to drive home a few points: microservice != polyglot, importance of continuous delivery and high-quality dev tools, and the usefulness of isolation as a core strategy to manage risk while scaling teams.
What is the level of experience someone attending this talk should have?
Approachable for all; probably most useful for people thinking about creating a microservice architecture or who are suffering from the consequences of a poorly design distributed monolith.
Tracks
-
Humane Leadership
A look at leadership with an emphasis on empathy, taking chances and building other leaders within organizations and teams
-
Developer Experience: The Art and Science of Reducing Friction
Explore how to reduce developer friction between teams and stakeholders.
-
Blameless Culture
Absorb the lessons learned from failures and outages in a human-centric process.
-
Modern Computer Science in the Real World
Learn how companies are applying recent CS research to tackle concurrency, distributed data, and coordination.
-
Architectures You’ve Always Wondered About
Join companies like Google, Netflix, Bloomberg, BBC, and more as they share an inside glimpse on their next-gen architectures and challenges of delivering at massive scale.
-
Bare Knuckle Performance
Learn from practitioners on the challenges and benefits of architecting for performance and much more.
-
Java - The Interesting Bits
Learn the new features in the recent and near-future releases of Java and the JVM and what they offer.
-
Ethical Considerations in Consciously Designed Software
Design considerations for various contexts, locations, security and privacy requirements.
-
Operating Microservices
Learn from practitioners operating and evolving systems in performance demanding environments.
-
Shift-Left Cybersecurity: Developer Accountability for Security
Learn how to make security an inherent part of the software development process.
-
Native Compilation Is Back (A Look at Non-Vm Compilation Targets)
Issues with native compilation for in browser-based and server-side environments
-
Troubleshooting in Production
Learn debugging strategies for complex and high stakes environments where standard debuggers and profilers fail.
-
Predictive Architectures and ML
Learn about cutting-edge ML applications and their underlying architectures.
-
Mission Critical Data Engineering
Explore a variety of data engineering use-cases and applications
-
Production Readiness
Observability, emergency response, capacity planning, release processes, and SLOs for availability and latency.