Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

The flow and architecture of web based applications using hexagonal methodology

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Wird geladen in …3
×

Hier ansehen

1 von 43 Anzeige

The flow and architecture of web based applications using hexagonal methodology

Herunterladen, um offline zu lesen

The presentation's purpose is to inspire people to take a look at hexagonal architecture and their ways of work, rather then delving deeply into too much technical things like the architecture itself. There are many other topics that deal with the architecture

The presentation's purpose is to inspire people to take a look at hexagonal architecture and their ways of work, rather then delving deeply into too much technical things like the architecture itself. There are many other topics that deal with the architecture

Anzeige
Anzeige

Weitere Verwandte Inhalte

Ähnlich wie The flow and architecture of web based applications using hexagonal methodology (20)

Anzeige

Aktuellste (20)

The flow and architecture of web based applications using hexagonal methodology

  1. 1. THE FLOW AND ARCHITECTURE OF WEB BASED APPLICATIONS USING HE AGONAL METHODOLOGY HI MY NAME IS IVO AND TODAY I WANT TO SHARE WITH YOU X
  2. 2. FEATURES AND COMPLEXITY Decoupled Coupled Amount of Features / Time Complexity Growing Technical Debt
  3. 3. SO WHAT MAKES PEOPLE NOT CARE ABOUT THE RED ALERT?
  4. 4. PRESSURE FROM THE BOSS? WHERE ARE MY NEW FEATURES!?
  5. 5. PRESSURE FROM THE BOSS? WHY DO WE HAVE SO MANY BUGS!?
  6. 6. COMPLAINING STRESSES PEOPLE @stress#$%*@ @&^#$stress& $%*!!!!!
  7. 7. LEVELS OF ENTHUSIASM DROP RAPIDLY
  8. 8. RELUCTANCY TO LEARN, WORK AND IMPROVE PERSONAL KNOWLEDGE
  9. 9. SO ASK YOURSELF: WHAT CAN I DO TO WORK LESS AND MAKE THE BOSSMAN HAPPY?
  10. 10. ONE MORE THING IF YOU WERE YOUR OWN BOSS, WHAT WOULD MAKE YOU HAPPY?
  11. 11. SO WHAT IS THE ANSWER?
  12. 12. THINK ABOUT THE FUTURE OF YOUR APPLICATION IN THE BEGINNING
  13. 13. LEARN HOW TO BOOST YOUR APPLICATION AT ITS START, BY USING BETTER ARCHITECTURE
  14. 14. SO WHAT IS ARCHITECTURE
  15. 15. IS IT ACTUALLY A COMBINATION OF DIFFERENT PIECES OF CODE WORKING TOGETHER JUST ?LIKE A CLOCKWORK
  16. 16. MAYBE ID DOES, WE ARE NOT SURE SO MANY QUESTIONS AND THERE ARE SO MANY DIFFERENT ANSWERS
  17. 17. DIFFERENT OPINIONS
  18. 18. MV C HOLY GRAIL
  19. 19. M
  20. 20. M
  21. 21. M KNOWS HOW TO SAVE DATA IN YOUR DATABASE
  22. 22. V
  23. 23. V
  24. 24. V GENERATES OUTPUT PRESENTATION BASED ON THE DATA IN FROM THE MODEL
  25. 25. C
  26. 26. C
  27. 27. C HANDLES REQUESTS FROM THE VIEW AND UPDATES THE MODEL’S STATE
  28. 28. S
  29. 29. S
  30. 30. S SERVERS TO OFFLOAD TASKS FROM THE CONTROLLER AND ALSO HAS NO STATE
  31. 31. THE MYSTERIOUS PERSISTNACE STORAGE
  32. 32. Data flow both ways Data flow one way Data flow through a request WHAT PEOPLE DO
  33. 33. THE EQUIVALENT * * - EQUIVALENCE SYMBOL
  34. 34. WHAT THE BOSS THINKS
  35. 35. WHAT HAPPENS WHEN A CHANGE OCCURS CUT CUT CUT CUT REFACTOR
  36. 36. THE HEXAGON
  37. 37. R COMMUNICATION BETWEEN MODEL AND CORE DOMAIN
  38. 38. CD HOLDS THE BUSINESS LOGIC. UNDERSTANDABLE BY THE DOMAIN SPECIALISTS
  39. 39. Data flow both ways Data flow one way Data flow through an event bus WHAT IT CAN BE
  40. 40. DEPENDENCIES
  41. 41. A DIFFERENT PERSPECTIVE
  42. 42. THANK YOU FOR THE ATTENTION!

×