<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microservices on Manuel Bernhardt</title><link>https://manuel.bernhardt.io/tags/microservices/</link><description>Recent content in Microservices on Manuel Bernhardt</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 18 Feb 2023 20:54:16 +0100</lastBuildDate><atom:link href="https://manuel.bernhardt.io/tags/microservices/index.xml" rel="self" type="application/rss+xml"/><item><title>Tour de Lagom Part 1: Lagom and microservices</title><link>https://manuel.bernhardt.io/2017/06/05/tour-de-lagom-part-1-lagom-microservices/</link><pubDate>Mon, 05 Jun 2017 16:17:52 +0200</pubDate><guid>https://manuel.bernhardt.io/2017/06/05/tour-de-lagom-part-1-lagom-microservices/</guid><description>&lt;p>&lt;a href="https://www.lagomframework.com">Lagom&lt;/a> is a framework for building reactive microservices in Scala or Java with an emphasis on developer productivity. I&amp;rsquo;ve had a chance to work with it for some time and would like to share my impressions about it. This is going to take a bit longer than just one post, so you&amp;rsquo;re reading part one of a 3-part series:&lt;/p>
&lt;ul>
&lt;li>Part 1: Lagom and microservices&lt;/li>
&lt;li>Part 2: Lagom and reactive&lt;/li>
&lt;li>Part 3: Lagom and developer productivity&lt;/li>
&lt;/ul>
&lt;p>The idea is to cover most of what Lagom has to offer by looking at it at various angles. Let&amp;rsquo;s go!&lt;/p></description></item><item><title>The microservices marathon</title><link>https://manuel.bernhardt.io/2016/06/14/the-microservices-marathon/</link><pubDate>Tue, 14 Jun 2016 09:19:58 +0200</pubDate><guid>https://manuel.bernhardt.io/2016/06/14/the-microservices-marathon/</guid><description>&lt;p>Everyone is talking about microservices. And many people are betting on it. At this year&amp;rsquo;s &lt;a href="https://voxxeddays.com/vienna/">Voxxed Days Vienna&lt;/a> over 60% of the submissions contained the word microservices. At JAX 2016 in Mainz, the word microservices was spoken out aloud on average 40 times per minute accross the entire venue. It&amp;rsquo;s hard to go one day on Twitter without seeing microservices in the stream.&lt;/p>
&lt;p>In this post I&amp;rsquo;ll first try to answer the question of why there is a need for microservices (in some settings) and then I&amp;rsquo;d like to talk a bit about what I think is a neglected issue in all the hype surrounding the topic these days: the feasability of organizational adoption of microservices. It is one thing to have the tools to microservice and another one entirely to be able to get an organization to think and act in terms compatible with the vision promised by the microservice architecture.&lt;/p></description></item></channel></rss>