Majestic Modular Monoliths by Axel Fontaine

Поділитися
Вставка
  • Опубліковано 13 лис 2018
  • Subscribe to Devoxx on UA-cam @ bit.ly/devoxx-youtube
    Like Devoxx on Facebook @ / devoxxcom
    Follow Devoxx on Twitter @ / devoxx
    Microservices are everywhere. Everyone seems to be either going into that direction or is talking about doing so. But are they really the best choice for you?
    Developers! Architects! Buckle up as we're going to cut through the hype. Instead of going all-in on microservices or all-in on big ball of mud, we'll introduce a third choice: the Majestic Modular Monolith! We'll look at what it brings to the table, when it may be a good fit and how it compares to the other two approaches in terms of code organization, productivity, scalability and much more. We'll look at how this can be designed and implemented in practice. Get ready. We won't shy away from the hard questions.
    Axel Fontaine
    From Boxfuse GmbH
    Axel Fontaine is the founder and CEO of Boxfuse (boxfuse.com), the easiest way to deploy JVM, Node.js and Go applications to AWS, and the creator of Flyway (flywaydb.org), the open-source tool that makes database migrations easy.
    Axel is an entrepreneur, a Continuous Delivery expert, an Immutable Infrastructure expert, a Java Champion, a JavaOne Rockstar, a regular speaker at many large international conferences, a trainer and an author.
  • Наука та технологія

КОМЕНТАРІ • 23

  • @waldoaraya3058
    @waldoaraya3058 2 роки тому +25

    This talk is pure Gold. I can't belive that has only 12.000 views! This talk must be mandatory for every software developer. Thaks for this tremendous knowledge

  • @independent408
    @independent408 3 роки тому +6

    Absolutelly agree with you. Also, I have one good point to add - Micro-Compilations. This approach allows to minimize development iteration up to 6 seconds for desktop application. You make a change into file, press shortcut in IDE, script performs MicroCompilation of current file (and related things), you Alt-Tab to application, press F5, and get your UI updated for change. No loose of context, no loose of focus, very very fast. With MicroCompilations I was able to develop very sophisticated logic in very short terms. Can't imagine how much time will be needed if you recompile whole module for every change, and restart whole application every time.

  • @maneshipocrates2264
    @maneshipocrates2264 6 місяців тому

    Powerful talk IMO. Everybody grappling with whether to start with Monolith or Microservices should watch this,

  • @ndewet
    @ndewet 5 років тому +19

    A masterclass in my opinion. Especially relevant in my home country of New Zealand where we have a small population (under 5 million) so the vast majority of software written to serve subsets of that population does not need the rather costly benefits that come with microservices.

  • @ayanSaha13291
    @ayanSaha13291 2 роки тому +1

    This talk is absolutely marvelous! Thanks.

  • @xprt642
    @xprt642 5 років тому +4

    Very nice talk. This works also on PHP.

  • @thurstonmorris7299
    @thurstonmorris7299 3 роки тому +2

    Great talk.

  • @astrocrm
    @astrocrm 5 років тому +7

    Excellent talk! Microservices can be a huge pitfall.

  • @cj5454
    @cj5454 Рік тому +2

    This video scaled amazingly well. Amazon just dropped their own MicroService architecture for Monolith and it saved them 90% of costs

  • @extendetBG
    @extendetBG Рік тому

    Still accurate and trending! Also, asymmetrical scaling blew my mind.

  • @YBWang-pi9qq
    @YBWang-pi9qq 2 роки тому +1

    Confused by the hypes like micro service, architechture, etc, This talk is really practical and clear about SW architechture for me.
    12:00 When use Monolith, when go to microservice?
    Micro service fit all?
    most small organizations or Apps do not need the complexity of microservice.

  • @anastasiosioannidis7240
    @anastasiosioannidis7240 2 роки тому +1

    14.12 - Can one help me understand how the services entanglement is mitigated with DDD?
    Still we'll have to make the same amount of calls to services to get the aggregates

  • @kahnfatman
    @kahnfatman Рік тому +4

    Microservice is a plaque.

  • @nyrtzi
    @nyrtzi 4 роки тому +8

    I'd think long and hard about if one wants to be using the database for queues.

    • @Dragiux
      @Dragiux 2 роки тому

      Much like filesystems should not be used as databases, there are some things that just happen.

    • @alivateRocket
      @alivateRocket 2 роки тому +1

      Why? If it works, you can always change to a dedicated queue system when your scale requires it. And only for the entities that have that scale.

  • @7th_CAV_Trooper
    @7th_CAV_Trooper Рік тому +2

    RDBMS does not magically handle consistency for you. You need to know the isolation level tradeoffs and how to deal with the inevitable data inconsistency.

  • @stoic8415
    @stoic8415 4 роки тому +3

    How will the modules interact with each other via api? Is there a more detailed description of these methods or maybe a test project?

    • @anask9942
      @anask9942 2 роки тому +5

      API here means the interface of the module which are the classes exposed by the module to the outside

    • @waldoaraya3058
      @waldoaraya3058 2 роки тому +1

      @@anask9942 thanks a lot for you answer