From DDD & N-tier architecture to akka

1. From DDD & N-TIER
architecture to Akka

2. Typical
software
design for large
scale business
logics & large
scale teams
these days

3. DDD design
patterns
principles
It’s all about
Single Responsibility
Principle &
ubiquitous domain
language

4. DDD design
patterns
principles
It’s all about
Single Responsibility
Principle & unified
naming convention

5. N-TIER design
patterns
principles
It’s all about
Layering &
Dependencies

6. But what about scaling, access &
throughput + resiliency?

7. But what about scaling, access &
throughput + resiliency?
That’s where Akka play in the big league

8. Capacity to scale
fall down
ultimately in your
capacity to process
tasks without
blocking shared
resources

9. Capacity to scale
fall down
ultimately in your
capacity to process
tasks without
blocking shared
resources
That’s why we use
REDIS, that’s why we
use SQL. They are
layers to prevent
concurrency problems,
but delegating this to
those technology, just
add latency in our
code.

10. Akka gets that
and build a
framework to
make any software
components
ready to avoid
scaling issues
and increase
throughput

11. That’s what typical
architecture don’t
have. Built-in
techniques to deal
with it at the
component level
BLOCKING
(increase throughput)

12. That’s what typical
architecture don’t
have. Built-in
techniques to deal
with it at the
component level
BLOCKING
(increase throughput)

13. That’s what typical
architecture don’t
have. Built-in
techniques to deal
with it at the
component level
RESILIENCY

14. That’s what typical
architecture don’t
have. Built-in
techniques to deal
with it at the
component level
MUTABILITY (CQRS)
Descriptive mutation components

15. What it could looks
like from an holistic view
of it
- Presentations layers
- Business logic layer
- Data lake, warehouse
- Machine learning area
All in real-time

16. It doesn’t change
the basics of good
coding design
Which all these
frameworks are
implementations of
those good patterns
SOLID

17. THANK YOU