blog.frankel.ch/chopping-monolith

Preview meta tags from the blog.frankel.ch website.

Linked Hostnames

15

Thumbnail

Search Engine Appearance

Google

https://blog.frankel.ch/chopping-monolith

Chopping the monolith

If you attend conferences or read technical articles, you could think that microservices are the correct and only way to build a system at the moment. Despite some pushback from cooler heads, the default architecture is microservices. In this post, I’d like to argue why it’s wrong. I’ll first get back to the origin of microservices and the fundamental reason to use them. Then, I’ll describe why microservices don’t fit most organizations' structures. Afterward, I̵



Bing

Chopping the monolith

https://blog.frankel.ch/chopping-monolith

If you attend conferences or read technical articles, you could think that microservices are the correct and only way to build a system at the moment. Despite some pushback from cooler heads, the default architecture is microservices. In this post, I’d like to argue why it’s wrong. I’ll first get back to the origin of microservices and the fundamental reason to use them. Then, I’ll describe why microservices don’t fit most organizations' structures. Afterward, I̵



DuckDuckGo

https://blog.frankel.ch/chopping-monolith

Chopping the monolith

If you attend conferences or read technical articles, you could think that microservices are the correct and only way to build a system at the moment. Despite some pushback from cooler heads, the default architecture is microservices. In this post, I’d like to argue why it’s wrong. I’ll first get back to the origin of microservices and the fundamental reason to use them. Then, I’ll describe why microservices don’t fit most organizations' structures. Afterward, I̵

  • General Meta Tags

    9
    • title
      Chopping the monolith
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • HandheldFriendly
      true
    • viewport
      width=device-width, initial-scale=1.0
  • Open Graph Meta Tags

    8
    • og:site_name
      A Java geek
    • og:type
      website
    • og:title
      Chopping the monolith
    • og:description
      If you attend conferences or read technical articles, you could think that microservices are the correct and only way to build a system at the moment. Despite some pushback from cooler heads, the default architecture is microservices. In this post, I’d like to argue why it’s wrong. I’ll first get back to the origin of microservices and the fundamental reason to use them. Then, I’ll describe why microservices don’t fit most organizations' structures. Afterward, I̵
    • og:url
      https://blog.frankel.ch/chopping-monolith/
  • Twitter Meta Tags

    7
    • twitter:card
      summary_large_image
    • twitter:site:id
      nicolas_frankel
    • twitter:title
      Chopping the monolith
    • twitter:description
      If you attend conferences or read technical articles, you could think that microservices are the correct and only way to build a system at the moment. Despite some pushback from cooler heads, the default architecture is microservices. In this post, I’d like to argue why it’s wrong. I’ll first get back to the origin of microservices and the fundamental reason to use them. Then, I’ll describe why microservices don’t fit most organizations' structures. Afterward, I̵
    • twitter:url
      https://blog.frankel.ch/chopping-monolith/
  • Item Prop Meta Tags

    10
    • name
      Nicolas Fränkel
    • givenName
      Nicolas
    • familyName
      Fränkel
    • jobTitle
      Head of Developer Advocacy
    • worksFor
      Apache APISIX
  • Link Tags

    12
    • alternate
      https://blog.frankel.ch/feed.xml
    • url
      https://blog.frankel.ch/chopping-monolith/
    • me
      https://mastodon.top/@frankel
    • me
      https://github.com/nfrankel
    • shortcut icon
      /assets/cup.ico

Links

34