Главная
Study mode:
on
1
Intro
2
Jetcom
3
Microservices
4
Chaos Engineering
5
Definitions
6
Event sourcing
7
How did Jet decide on microservices
8
Why did Jet choose Fsharp
9
How Fsharp helped Jet
10
Option types
11
Perl not being readable
12
Why Fsharp
13
Shawns Fsharp talk
14
Be functional
15
Dont try abstract microservices
16
Dont do this
17
Separate them
18
Staging
19
Torch
20
Summary
21
More information
Description:
Explore the lessons learned in developing a cloud-based event-driven microservices architecture at Jet.com in this 55-minute conference talk. Delve into chaos engineering, event sourcing, and the decision-making process behind choosing microservices and F# as the programming language. Learn about the benefits of functional programming, option types, and the importance of readability in code. Discover best practices for microservice design, including separation and staging strategies. Gain valuable insights on what works and what doesn't in real-world event-driven microservices implementation, and find out where to obtain more information on the subject.

Patterns and Practices for Real-World Event-Driven Microservices

NDC Conferences
Add to list
0:00 / 0:00