home.social

#modulith โ€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #modulith, aggregated by home.social.

  1. ๐—™๐—น๐—ฒ๐˜…๐—ถ๐—ฏ๐—น๐—ฒ ๐—”๐—ฟ๐—ฐ๐—ต๐—ถ๐˜๐—ฒ๐—ธ๐˜๐˜‚๐—ฟ ๐—ฒ๐—ป๐˜๐˜€๐˜๐—ฒ๐—ต๐˜ ๐—ป๐—ถ๐—ฐ๐—ต๐˜ ๐—ฑ๐˜‚๐—ฟ๐—ฐ๐—ต ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ ๐—ฎ๐—น๐—น๐—ฒ๐—ถ๐—ป โ€“ ๐—œ๐—ป๐˜๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฒ๐˜„ ๐—บ๐—ถ๐˜ ๐—˜๐—ฏ๐—ฒ๐—ฟ๐—ต๐—ฎ๐—ฟ๐—ฑ ๐—ช๐—ผ๐—น๐—ณ๐—ณ ๐˜‚๐—ป๐—ฑ ๐—™๐—ฎ๐—น๐—ธ ๐—ฆ๐—ถ๐—ฝ๐—ฝ๐—ฎ๐—ฐ๐—ต ๐ŸŽค
    Machen #Microservices Systeme automatisch flexibler? Nicht unbedingt. Im Interview erklรคren @ewolff und @sippsack, warum echte Flexibilitรคt bereits bei fachlichen Grenzen und Architekturentscheidungen beginnt.

    ๐Ÿ’ก Themen:
    โ€ข #DDD & Flexibilitรคt
    โ€ข #Modulith vs. #Microservices
    โ€ข praktische Schritte zu flexibleren Systemen

    ๐Ÿ‘‰ t1p.de/bf4sm

    #SAF2026 #iSAQB #Softwarearchitektur

  2. ๐—™๐—น๐—ฒ๐˜…๐—ถ๐—ฏ๐—น๐—ฒ ๐—”๐—ฟ๐—ฐ๐—ต๐—ถ๐˜๐—ฒ๐—ธ๐˜๐˜‚๐—ฟ ๐—ฒ๐—ป๐˜๐˜€๐˜๐—ฒ๐—ต๐˜ ๐—ป๐—ถ๐—ฐ๐—ต๐˜ ๐—ฑ๐˜‚๐—ฟ๐—ฐ๐—ต ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ ๐—ฎ๐—น๐—น๐—ฒ๐—ถ๐—ป โ€“ ๐—œ๐—ป๐˜๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฒ๐˜„ ๐—บ๐—ถ๐˜ ๐—˜๐—ฏ๐—ฒ๐—ฟ๐—ต๐—ฎ๐—ฟ๐—ฑ ๐—ช๐—ผ๐—น๐—ณ๐—ณ ๐˜‚๐—ป๐—ฑ ๐—™๐—ฎ๐—น๐—ธ ๐—ฆ๐—ถ๐—ฝ๐—ฝ๐—ฎ๐—ฐ๐—ต ๐ŸŽค
    Machen #Microservices Systeme automatisch flexibler? Nicht unbedingt. Im Interview erklรคren @ewolff und @sippsack, warum echte Flexibilitรคt bereits bei fachlichen Grenzen und Architekturentscheidungen beginnt.

    ๐Ÿ’ก Themen:
    โ€ข #DDD & Flexibilitรคt
    โ€ข #Modulith vs. #Microservices
    โ€ข praktische Schritte zu flexibleren Systemen

    ๐Ÿ‘‰ t1p.de/bf4sm

    #SAF2026 #iSAQB #Softwarearchitektur

  3. ๐—™๐—น๐—ฒ๐˜…๐—ถ๐—ฏ๐—น๐—ฒ ๐—”๐—ฟ๐—ฐ๐—ต๐—ถ๐˜๐—ฒ๐—ธ๐˜๐˜‚๐—ฟ ๐—ฒ๐—ป๐˜๐˜€๐˜๐—ฒ๐—ต๐˜ ๐—ป๐—ถ๐—ฐ๐—ต๐˜ ๐—ฑ๐˜‚๐—ฟ๐—ฐ๐—ต ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ ๐—ฎ๐—น๐—น๐—ฒ๐—ถ๐—ป โ€“ ๐—œ๐—ป๐˜๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฒ๐˜„ ๐—บ๐—ถ๐˜ ๐—˜๐—ฏ๐—ฒ๐—ฟ๐—ต๐—ฎ๐—ฟ๐—ฑ ๐—ช๐—ผ๐—น๐—ณ๐—ณ ๐˜‚๐—ป๐—ฑ ๐—™๐—ฎ๐—น๐—ธ ๐—ฆ๐—ถ๐—ฝ๐—ฝ๐—ฎ๐—ฐ๐—ต ๐ŸŽค
    Machen #Microservices Systeme automatisch flexibler? Nicht unbedingt. Im Interview erklรคren @ewolff und @sippsack, warum echte Flexibilitรคt bereits bei fachlichen Grenzen und Architekturentscheidungen beginnt.

    ๐Ÿ’ก Themen:
    โ€ข #DDD & Flexibilitรคt
    โ€ข #Modulith vs. #Microservices
    โ€ข praktische Schritte zu flexibleren Systemen

    ๐Ÿ‘‰ t1p.de/bf4sm

    #SAF2026 #iSAQB #Softwarearchitektur

  4. ๐—™๐—น๐—ฒ๐˜…๐—ถ๐—ฏ๐—น๐—ฒ ๐—”๐—ฟ๐—ฐ๐—ต๐—ถ๐˜๐—ฒ๐—ธ๐˜๐˜‚๐—ฟ ๐—ฒ๐—ป๐˜๐˜€๐˜๐—ฒ๐—ต๐˜ ๐—ป๐—ถ๐—ฐ๐—ต๐˜ ๐—ฑ๐˜‚๐—ฟ๐—ฐ๐—ต ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ ๐—ฎ๐—น๐—น๐—ฒ๐—ถ๐—ป โ€“ ๐—œ๐—ป๐˜๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฒ๐˜„ ๐—บ๐—ถ๐˜ ๐—˜๐—ฏ๐—ฒ๐—ฟ๐—ต๐—ฎ๐—ฟ๐—ฑ ๐—ช๐—ผ๐—น๐—ณ๐—ณ ๐˜‚๐—ป๐—ฑ ๐—™๐—ฎ๐—น๐—ธ ๐—ฆ๐—ถ๐—ฝ๐—ฝ๐—ฎ๐—ฐ๐—ต ๐ŸŽค
    Machen #Microservices Systeme automatisch flexibler? Nicht unbedingt. Im Interview erklรคren @ewolff und @sippsack, warum echte Flexibilitรคt bereits bei fachlichen Grenzen und Architekturentscheidungen beginnt.

    ๐Ÿ’ก Themen:
    โ€ข #DDD & Flexibilitรคt
    โ€ข #Modulith vs. #Microservices
    โ€ข praktische Schritte zu flexibleren Systemen

    ๐Ÿ‘‰ t1p.de/bf4sm

    #SAF2026 #iSAQB #Softwarearchitektur

  5. ๐—™๐—น๐—ฒ๐˜…๐—ถ๐—ฏ๐—น๐—ฒ ๐—”๐—ฟ๐—ฐ๐—ต๐—ถ๐˜๐—ฒ๐—ธ๐˜๐˜‚๐—ฟ ๐—ฒ๐—ป๐˜๐˜€๐˜๐—ฒ๐—ต๐˜ ๐—ป๐—ถ๐—ฐ๐—ต๐˜ ๐—ฑ๐˜‚๐—ฟ๐—ฐ๐—ต ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ ๐—ฎ๐—น๐—น๐—ฒ๐—ถ๐—ป โ€“ ๐—œ๐—ป๐˜๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฒ๐˜„ ๐—บ๐—ถ๐˜ ๐—˜๐—ฏ๐—ฒ๐—ฟ๐—ต๐—ฎ๐—ฟ๐—ฑ ๐—ช๐—ผ๐—น๐—ณ๐—ณ ๐˜‚๐—ป๐—ฑ ๐—™๐—ฎ๐—น๐—ธ ๐—ฆ๐—ถ๐—ฝ๐—ฝ๐—ฎ๐—ฐ๐—ต ๐ŸŽค
    Machen #Microservices Systeme automatisch flexibler? Nicht unbedingt. Im Interview erklรคren @ewolff und @sippsack, warum echte Flexibilitรคt bereits bei fachlichen Grenzen und Architekturentscheidungen beginnt.

    ๐Ÿ’ก Themen:
    โ€ข #DDD & Flexibilitรคt
    โ€ข #Modulith vs. #Microservices
    โ€ข praktische Schritte zu flexibleren Systemen

    ๐Ÿ‘‰ t1p.de/bf4sm

    #SAF2026 #iSAQB #Softwarearchitektur

  6. Morgen findet mein #JUG Talk zu #Spring #Modulith statt. ๐Ÿ˜ฑ

    Habe schon lange keinen #Java-Vortrag mehr gemacht, deswegen kenn ich mich mit den Community-Konventionen nicht mehr so aus.

    Was meint ihr: Reicht es, wenn ich Live Coding mache, oder lieber Slides?

  7. Good thing @odrotbohmโ€™s workshop/talk is a long one for this long flight Iโ€™m onโ€ฆ

    youtu.be/k3o1nSh3g2Q

    #Java #DDD #Modulith #Spring

  8. Imagine we have a #java #modulith / #Monolit, am I correct that the following illustration is a good pattern?
    1. a Controller only access its respective Service
    2. a Service can access its respective Repository
    3. a Service can access other Services
    4. a Controller and Repository are not allowed to access other Controller or Repositories

    This ensures that there is only a Service layer where the business logic is stored.
    Are there any downsides I miss?

  9. Hab gestern auf der @jugka รผber den Microservice Trade-Off gesprochen. Die Leute waren gut drauf. Einige bekannte Gesichter aus der Karlsruher Bubble. Und ich liebe den Veranstaltungsbereich bei @synyx und die Technik-Crew!

    Hier sind die Folien:

    speakerdeck.com/indyarni/der-m

    #SoftwareArchitecture #coding #microservices #modulith

  10. Two nice quotes from "Strategic Monoliths and Microservices" by @VaughnVernon and Tomasz Jaskula:

    "๐—–๐—ต๐—ผ๐—ผ๐˜€๐—ถ๐—ป๐—ด ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ๐˜€ ๐—ณ๐—ถ๐—ฟ๐˜€๐˜ ๐—ถ๐˜€ ๐—ฑ๐—ฎ๐—ป๐—ด๐—ฒ๐—ฟ๐—ผ๐˜‚๐˜€. ๐—–๐—ต๐—ผ๐—ผ๐˜€๐—ถ๐—ป๐—ด ๐— ๐—ผ๐—ป๐—ผ๐—น๐—ถ๐˜๐—ต๐˜€ ๐—ณ๐—ผ๐—ฟ ๐˜๐—ต๐—ฒ ๐—น๐—ผ๐—ป๐—ด ๐˜๐—ฒ๐—ฟ๐—บ ๐—ถ๐˜€ ๐—ฎ๐—น๐˜€๐—ผ ๐—ฑ๐—ฎ๐—ป๐—ด๐—ฒ๐—ฟ๐—ผ๐˜‚๐˜€."

    "๐— ๐—ผ๐—ฑ๐˜‚๐—น๐—ฒ๐˜€ ๐—ณ๐—ถ๐—ฟ๐˜€๐˜, ๐—ฑ๐—ฒ๐—ฝ๐—น๐—ผ๐˜†๐—บ๐—ฒ๐—ป๐˜ ๐—น๐—ฎ๐˜€๐˜"

    #microservices #modulith #SoftwareArchitecture #SoftwareEngineering #coding

  11. I am trying to compile the different trade-offs you make when choosing between a #Modulithโ€Žic and #Microservice Architecture, considering different aspects of that decision. Find a first draft below. Feedback welcome in the Gist's comments!

    gist.github.com/odrotbohm/b9d7

  12. I don't know what to say, but it's been right in front of us, all the time. #moNOlith #moDUlith

  13. 1/ First time trying #SpringModulith since its early versions.
    Setting it up to verify and enforce the module structure was really fast and easy. So was explicitly exposing module APIs. It has other cool features, that we may need in the future but this is its core and it does it really well and simple. Thx @odrotbohm !

    #SoftwareArchitecture #modulith #Spring

  14. Schon einmal von Spring Modulith gehรถrt? ๐Ÿš€
    In meinem neuen Blogartikel erfรคhrst du, was ein #Modulith eigentlich ist und erhรคltst ein paar Tipps, wie du Spring Modulith mit #Kotlin und der hexagonalen Architektur einsetzt.

    Was erfรคhrst du im Blogartikel?
    โ–ช๏ธ#Spring Modulith hilft dir deine Module sauber zu entkoppelt
    โ–ช๏ธKombination von Spring Modulith mit der hexagonalen Architektur
    โ–ช๏ธLegacy-Systeme

    GroรŸes Lob an das Spring-Team und natรผrlich auch an @odrotbohm.

    Artikel: codecentric.de/wissens-hub/blo

  15. Quote from "Strategic Monoliths and Microservices" by @VaughnVernon and Tomasz Jaskula:

    "Imagining that Microservices automatically deliver higher performance is
    wrong. The only way to understand the trade-offs is to measure. In-process
    method invocations are faster than network operations."

    I'm reading the book to get more input for a potential talk with working title "The Microservice Tradeoff".

    #microservices #monolith #modulith #SoftwareArchitecture #coding

  16. The hype about microservices left unhealthy expectations with some people. We have to frequently justify why we did not slice a piece of software into microservices

    "Why didn't you just split it into services?"

    "just" as if it's the default and easiest way to do things

    We are met with blank faces when we explain:
    "It's too tightly coupled, there are no apparent fracture planes. There's no good reason to justify the trade-off of the overhead..."

    #microservices #modulith #SoftwareArchitecture

  17. So smart! #ApacheKaraf has rebranded as "The #Modulith Runtime" - Modular Monoliths "It is the way" #Java

  18. It's often a good thing to slice your software into multiple services - but be sure to make it for the right reasons and always consider the trade-off.

    #modulith #microservices #SoftwareArchitecture #SoftwareEngineering #DevOps #DDD

  19. * "One bounded context from DDD equals one service"
    * "When good DevOps automatisms are in place, more services don't cause overhead"

    Falling for these misconceptions can lead to
    * Unnecessary complexity
    * Huge maintenance and operations overhead
    * New performance problems
    * Hidden or unclear dependencies and side effects
    * Distributed monoliths

    #modulith #microservices #SoftwareArchitecture #SoftwareEngineering #DevOps #DDD

  20. 1/ There are some misconceptions about distributed systems ("microservice") architecture that I encountered repeatedly in my projects:

    * "The only way to modularize your software is to split it into multiple deployment units - 'services'"
    * "Services have to be small"
    * "Many small services are easier to maintain than few big services"
    * "There are no downsides to cutting services into smaller services"
    * "Using microservices solves all performance problems"

    #modulith #microservices

  21. I disagree with most of the assumptions made and consequences derived from those in this talk but I think itโ€™s highly interesting nonetheless. Especially on a meta level on how our day-to-day tech stack environment shapes our thinking about whatโ€™s (im)possible. #rails #modulith youtu.be/olxoNDBp6Rg

  22. Auf meiner Challenge Entwickler in 60 Sekunden auf ein neues Projekt onzuboarden erkunde ich weiter #DotnetAspire fรผr #Dotnet.

    Erster Schritt: Eine einfache Konfiguration fรผr einen existierenden #Modulith

    zyrr.io/blog/2024/2024-07-17-a

  23. Nach dem Meetup ist vor dem Meetup. Am 14.5 gehts weiter. @odrotbohm wird uns #spring #modulith nรคher bringen. Infos findet ihr schon auf unserer Website, die Anmeldung wird im Laufe des Tage online gehen! Aber aufgepasst, diesmal Treffen wir uns schon am Dienstag! jug-pb.gitlab.io/blog/2024/spr #java #usergroup

    Und die Anmeldung ist freigeschaltet: eventbrite.com/e/spring-moduli

  24. Personally working with hexagonal architecture for the first time and recognizing its problems, I was working on a way to mitigate the problems by combining it in a meaningful way with the modulithic approach.

    Thankfully a colleague pointed me to this article by @odrotbohm delivering a solution to this exact problem. And also describing it in a very comprehensible way.

    odrotbohm.de/2023/07/sliced-on

    #hexagonalArchitecture #modulith

  25. ๐Ÿ“ข #Spring #Modulith 0.6 is out! A ton of great new features, but the biggest news beingโ€ฆ ๐Ÿฅ

    We're going to become non-experimental! ๐Ÿ”ฅ 1.0 M1 right after Spring Boot 3.1 GA. More info here: spring.io/blog/2023/05/02/spri, 0.6 changelog github.com/spring-projects-exp ๐Ÿƒ๐Ÿ“ฆ