- Архитектура приложений и веб-фреймворки; - Монолит или микросервисы? - Разбор архитектуры, которая работает; - Частые ошибки при построении архитектуры; - Как правильная архитектура экономит деньги?

1. The working architecture
of Web applications
Viktor Turskyi
CEO at WebbyLab
2019

2. Viktor Turskyi
● CEO and architect at WebbyLab
● 15 years in software development
● Delivered more than 60 projects of
different scale

3. I want to talk about
● The approach which we polish for 8 years already
● How to build large and small web applications with it
● How we use the same architecture for NodeJs, PHP, Perl web application
● Why we choose Monolith over Microservices first.
● Show real code, not only diagrams.
● What framework to choose.
● How all of it saves us money.

4. Why we choose monolith by default?

5. The most popular architecture is...

6. Big Ball of Mud
http://www.laputan.org/mud/mud.html#BigBallOfMud

7. If Monolith is a big ball of mud.
Will it be better with Microservices?

8. Microservices:
Distributed big ball of mud

10. "If you cannot build a monolith what makes you think that you
can build Distributed Microservices"
Simon Brown

12. Microservice architecture visualized
https://twitter.com/ThePracticalDev/status/845285541528719360

13. Microservices drawbacks
● High operational complexity (increases costs)
● Extremely hard to support transactions (risks of inconsistencies)
● Distribution issues (harder to program)
● Traceability issues (harder to debug)
● Technology diversity (mixing languages increases support costs,
standardization issues, hiring issues etc)
● Versions compatibility issues (harder to track all dependencies in consistent
state, reduces iterations speed)
● You need more experienced team (hiring issues)

14. Martin Fowler:
● But when your components are services with remote communications, then
refactoring is much harder than with in-process libraries.
● Another issue is If the components do not compose cleanly, then all you are
doing is shifting complexity from inside a component to the connections
between components. Not just does this just move complexity around, it
moves it to a place that's less explicit and harder to control.
https://martinfowler.com/bliki/MonolithFirst.html

15. Robert Martin:
“The job of architect is not to make decision, the job of the architect is to
defer decisions as long as possible”
“Good architecture maximizes number of decisions not made”
https://www.youtube.com/watch?v=o_TH-Y78tt4

16. What is Monolith?

17. Usually it looks like

19. Which web-framework to choose?

20. It doesn’t matter!

21. Your application architecture should not depend on a
web framework

22. Web frameworks we use
NodeJs: Express
PHP: Slim3
Perl : Mojolicious

23. MVC (from wikipedia)

24. Where to place this code? Model or Controller?

25. Fat Stupid Ugly Controllers
“The M in MVC: Why Models are Misunderstood and Unappreciated” Pádraic
Brady
http://blog.astrumfutura.com/2008/12/the-m-in-mvc-why-models-are-misunderstoo
d-and-unappreciated/

26. Is Model (MVC) and Domain Model the same?

27. Model (from MVC)/Domain Logic
● Domain model
● Transaction script
● Table module
● Service layer

29. Controllers
Services
Domain model
Data access
layer
Dispatcher
Layers

30. The way of thinking about Controllers
● Extremely thin layer
● Protects underneath layers from everything related to HTTP
● If you change JSON to XML (or even CLI), only controllers should be rewritten

31. The way of thinking about Domain Model
● Belongs to Model layer of MVC
● The core part of your application
● You have almost all of your business logic here (not only database access)!!!
● Knows nothing about service layer and upper layers
● Responsible for data storing and data integrity
● Fine grained API (not suited for remote invocation)

32. The way of thinking about Services
● Belongs to Model layer of MVC
● Contains application logic
● Does not trust any incoming params
● You should keep thin if possible
● Knows nothing about controllers/transport/UI.
● Use cases based API
● Knows about context (what user asks for data)
● Knows when and how to notify user (emails etc)
● Does coordination and security
● Coarse grained API (well suited for remote invocation)

33. ● Web framework independent layer of domain logic
● Learn once, write everywhere
● Well structured
● Works with large and small projects
● Hard to find existing framework which does the the same work.
Why own architecture?

34. Where do we use this architecture?
● Perl projects (Mojolicious web framework)
● PHP projects (Slim web framework)
● NodeJs (Express web framework)

35. Core patterns in the architecture
Application level (Martin Fowler):
● MVC
● Service layer
● Domain model
Class level (GoF):
● Template method
● Command

36. How do we cook the service layer?

37. Rule 1: Separate service class for each endpoint

38. Real code (with meta programming)

39. NodeJs example of a Service class

41. Base class (the simplest version)

42. “run” method
Template method in base class
Guarantees that all procedures are kept:
● Data was validated
● “execute” will be called only after validation
● “execute” will receive only clean data
● Checks permissions before calling “execute”
● Throws exception in case of validation errors.
Can do extra work like caching validator objects, etc.

43. Perl example of a Service class

46. Rule 2: Unified approach to validation
● DO NOT TRUST ANY USER INPUT! NEVER!!!
● Declarative validation
● Exclude all fields that do not have validation rules described
● Returns understandable error codes (neither error messages nor numeric
codes)
● It should be clear for the service user what is wrong with his data

47. We use LIVR for the validation
It supports:
● JavaScript
● Perl
● Perl 6
● PHP
● Go
● Erlang
● Python
● Ruby
● Java
● Lua
Details are here - http://livr-spec.org/

48. Rule 3: Never return objects directly
Whitelist every object
property:
1. You know what you
return (that no
internal/secret data there)
2. Your API is stable

49. It should be clear where any code should be! Otherwise you do not architecture.
One of the risks, than you can end up with an “Anemic domain model”
(https://www.martinfowler.com/bliki/AnemicDomainModel.html)
If you have a large project, this can be a reason of project failure as you will
implicitly switch to “transaction script” approach which is not well suited for large
applications.
Rule 4: Be aware of “Anemic domain model”
antipattern

50. Full example: User registration

53. User registration: controller/dispatcher

54. Controllers

55. Service

57. User model

58. Action model

59. Developers don't have to be full-stack but teams
should be.
https://martinfowler.com/bliki/PresentationDomainDataLayering.html

60. Main benefits
● NodeJs, PHP, Perl - the same architecture.
● Works with small and large projects
● Extremely flexible.
● Ease to start.
● Much cheaper for company to support the same approach on all projects.
● Web framework agnostic and based on micro frameworks which is easy to
learn for new person.
● Cheaper technology switch (for example from PHP to NodeJs).
● Cheaper communication.
● Knowledge sharing (larger core).
● Higher resources utilization.
● Monolith first approach and modular architecture allows us to switch to
Microservices later

61. Useful links
MonolithFirst by Martin Fowler
Microservice Trade-Offs by Martin Fowler
PresentationDomainDataLayering by Martin Fowler
The Principles of Clean Architecture by Uncle Bob Martin
The Clean Architecture by Robert Martin
Microservice Architecture at Medium

62. Telegram: @JABASCRIPT

63. Viktor Turskyi
viktor@webbylab.com
@koorchik @koorchik
https://webbylab.com