<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Paas on Cloudinthealps</title><link>https://cloudinthealps.mandin.net/tags/paas/</link><description>Recent content in Paas on Cloudinthealps</description><generator>Hugo</generator><language>fr-FR</language><lastBuildDate>Sat, 20 May 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudinthealps.mandin.net/tags/paas/index.xml" rel="self" type="application/rss+xml"/><item><title>PaaS and Managed Services</title><link>https://cloudinthealps.mandin.net/posts/paas-and-managed-services/</link><pubDate>Sat, 20 May 2017 00:00:00 +0000</pubDate><guid>https://cloudinthealps.mandin.net/posts/paas-and-managed-services/</guid><description>&lt;p&gt;If you know me, or have read some of my previous articles, you will know that I am a big fan of PaaS services.
They provide an easy way for architects and developers to design and build complex applications, without having to
spend a lot of time and resources on components that may be used out of the box. And it relieves us IT admins of having
to manage lower levels components and irrelevant questions. These questions are the ones that lead me to switch my
focus into cloud platforms a few years ago. One day I&amp;rsquo;ll write an article on my personal journey :)
Anyway, my subject today concerns the later stages of the application lifecycle. Let&amp;rsquo;s say we have designed and built a
truly modern app, using only PaaS services. To be concrete, here is a possible design.&lt;/p&gt;</description></item></channel></rss>