The Prime Video microservices to monolith story
Serverless first is a mistake. It should be &quot;serverless where it&#x27;s distinct advantages are actually useful&quot; which is way less common than people think.<p>Also generally the conception that building things with containers + k8s actually takes more time than serverless is a horseshit take IMO.
It doesn&#x27;t and if it&#x27;s taking you longer you are probably doing something wrong.<p>All the points noted in the slides etc just come from poor engineering leadership. i.e decisions&#x2F;choices, etc. Constaints do speed up development but they can be enforced by leadership, not by putting yourself in an endless pit of technical debt.<p>The only world where I can make a good case for serverless for small teams is if you have said poor leadership and serverless helps you escape their poor decision making.<p>Otherwise assuming you have the mandate necessary to get stuff built the right way just stick with the Boring Tech stack of JVM + PG + k8s. It solves all problems regardless of size, there are minimal decisions to be made (really just Spring or Quarkus atm) and you won&#x27;t spend time dicking around with half-baked serverless integration crap. Instead you can just use battle tested high performance libraries for literally everything.<p>Don&#x27;t get sucked into this serverless nonsense. It&#x27;s always been bad and it probably always will be. When it&#x27;s out of fashion Boring Tech will still be here.