Closing keynote by Jamie Allen
•Download as PPTX, PDF•
0 likes•141 views
The document discusses the goals and principles of microservices architectures, including isolation, resilience, asynchronous APIs, immutable deployments, exposing only necessary functionality through APIs, domain-driven design, and eventual consistency. It also notes additional operational complexity compared to monolithic architectures in areas like service discovery, failure management, and versioning. The Lagom framework is presented as providing tools that aim to help achieve these goals, such as event sourcing, service and persistence APIs, and development and production environments.
More Related Content
What's hot
What's hot (20)
Similar to Closing keynote by Jamie Allen
Similar to Closing keynote by Jamie Allen (20)
More from J On The Beach
More from J On The Beach (20)
Recently uploaded
Recently uploaded (20)
Closing keynote by Jamie Allen
- 1. The Future of Services Jamie Allen Sr. Director of Global Solutions Architects
- 2. Traditional application architectures and platforms are obsolete. Gartner
- 3. • Accelerate teams • Reduce dependency nightmares • Increase application throughput What are we trying to achieve? Calvin and Hobbes, Bill Waterston
- 4. • Size is irrelevant “Microservices” is a lousy term Bing Images
- 5. • At the API • In our source • For our data We want isolation Wikipedia, Creative Commons, created by DFoerster
- 6. We want realistic data management • Use CQRS and Event Sourcing, not CRUD • Transactions, especially distributed, will not work • Consistency is an anti-pattern at scale • Distributed locks and shared data will limit you • Data fabrics break all of these conventions Think in terms of compensation, not prevention. Kevin Webber, Lightbend
- 7. We want real resilience • It is merely whether or not something has been handled • It is only an external view, not internal where the failure has occurred • Resilience is being able to handle the “why” in a meaningful way • Threads • Within One Node • Across Many Nodes • Across Many Servers • Across Data Centers
- 8. We want asynchronous APIs • Synchronous request/response semantics are expensive • REST can be asynchronous, but still heavy • Each call requires a connection • Best used for external APIs • Stream-based interactions for inter-service communication where responses are not required • Message-based interactions for inter-service communication where responses are required
- 9. We want immutable deployments • We can bind a build of our application to a version of our configuration and always know what is currently running • You cannot edit configuration and keep running Dilbert, Scott Adams
- 10. We want to expose a “tip of the iceberg” • Users see the public API • The API hides much complexity MyBluePuzzle.org
- 11. We want Domain Driven Design • Knowing/understanding it is not necessarily a requirement • “Solving your pain” is the most important reason for microservices • In a greenfield project, Bounded Contexts and Aggregate Roots can help you to decompose the problem
- 12. We want to ACID v2 • Associativity, not Atomicity • Commutativity, not Consistency • Idempotent, not Isolation • Distributed, not Durable Wikipedia, Creative Commons, created by Weston.pace
- 13. • Proxying • Service Discovery • Stateless aggregation • Orchestration • Failure management • Versioning We will have additional operational complexity Complexityandotherbeasts.com
- 14. • Service API • Persistence API • Development environment • Production environment
- 15. • IO and communication • Streaming between services as a first-class concept • Higher level of resilience and scalability with no bloc king • Service is a Bounded Context in DDD Lagom Service API
- 16. • Event sourced (deltas) with Cassandra backend by default • No object/relational impedance mismatch • Can always replay to determine current state • Allows you to learn more from your data later • Persistent entity is an Aggregate Root in DDD • Can be overridden for CRUD if you want Lagom Persistence API
- 17. • Create single project definition in sbt, use runAll, incl udes: • In-memory Cassandra with own keyspaces • A service locator • A service gateway • Overload Mode: recompile and redeploy on save Development Environment
- 18. • Deployment • Monitoring • Scaling • Can test locally with ConductR then push to producti on • Launch multiple instances with a single command Production Environment (Lightbend RP)
Editor's Notes
- OPEN GAMBIT Multicore. Cloud computing. Containers. You’ll likely agree that the infrastructure for amazing scalability is in place, it’s been well funded. It’s the underpinning that’s required for enterprises to movie en masse to the cloud. But what are they moving? Applications. Applications that run their business, engage their customers, allow them to innovate and enter new markets. Without applications, this infinitely scalable infrastructure is nothing.
- a service locator (enables communication between services, registers itself on startup by name and address, no configuration needed) a service gateway (proxy for calling endpoints without knowing addresses in our app)