Welcome!

Machine Learning Authors: Yeshim Deniz, Liz McMillan, Pat Romanski, Elizabeth White, Corey Roth

Related Topics: Machine Learning , @CloudExpo, @ThingsExpo, @DevOpsSummit

Machine Learning : Blog Post

Do You Need PaaS for Cloud Microservices? By @IoT2040 | @DevOpsSummit [#DevOps]

Sergey Sverchkov of Altoros Offers His Analysis

Cloud computing adds flexibility to enterprise IT. When companies wish to take advantage of this, they are finding they need to turn to microservices instead of their traditional, monolithic architectures to accommodate frequent change.

Microservices can overcome the challenges presented by frequent change, "by splitting monoliths into multiple independent services, each with its own simple business logic," according to Sergey Sverchkov, a Solutions Architect with Altoros. Doing so leads to another issue: "choosing either PaaS or IaaS for microservices is an open question, " he says.

Sergey recently posted a thoughtful piece on the topic of PaaS vs. IaaS when implementing microservices on the Altoros blog. Altoros provides system integration services for a worldwide client base with the Cloud Foundry PaaS, yet Sverchov's piece takes a balanced view of which approach to take.

His fundamental point is that a DevOps team will be spending a lot of time monkeying around (my phrase, not Sergey's) when companies work straight to the bare infrastructure; taking the PaaS approach. "An automated PaaS is a bigger investment," he writes, "but it can shrink release cycles from weeks to hours and even eliminate some downsides of the microservices model."

In his post, Sergey covers six different areas regarding the implementation of microservices, and the differences between IaaS vs. PaaS in each of these areas, summarized as follows:

  1. One service for one job. With IaaS, "every service is deployed as an (IaaS) instance; DevOps ar responsible for configuring valid communication interfaces." With PaaS, "scalability can be controlled by a developer. Communication endpoints are served by the PaaS."

  1. Using different tools to implement different services. With IaaS, "DevOps needs to configure an application runtime." With PaaS, "an application runtime is automatically deployed in a PaaS container."

  1. Loose coupling. With IaaS, "The DevOps team manages IaaS instances used for service deployment." With PaaS, "containers are isolated elements for application deployment. Container lifecycle is managed by the Paas."

  1. Developer independence. With IaaS, " DevOps may need to create multiple IaaS environments for each of the development groups." Alternatively, with PaaS, development groups can be managed (using Cloud Foundry terminology) as "organizations" and "spaces."

  1. Continuous delivery. With IaaS, "DevOps engineers need to install and configure build-automation tools and integrate them with a project repository." Specifically with Cloud Foundry, "build-automation solutions can be deployed as a regular application."

  2. Integration with external services. With IaaS, "the DevOps team deploys external services. Applications connect (to them) using properties." With PaaS, "a service broker can be used to deploy and publish some external services. Service binding makes it easier to connect an application instance to external services."

In addition to the item about IaaS/PaaS and microservices, Sergey has authored a much longer technical whitepaper on te general topic of microservices vs. monolithic architectures, available through the blog section of the Altoros website.

I heard a lot of talk last year about major public cloud infrastructure providers starting to subsume PaaS into their offerings. Besides the potential for a new era of vendor lock-in, the IaaS vs. PaaS debate also involves significant functionality issues and questions of the skillsets, and more important, efficiency enterprise IT will have as the presence of cloud - public, private, and hybrid - increases within their organizations. Sergey's post adds value to this debate.

Contact Me on Twitter

Follow Cloud Expo on Twitter

More Stories By Roger Strukhoff

Roger Strukhoff (@IoT2040) is Executive Director of the Tau Institute for Global ICT Research, with offices in Illinois and Manila. He is Conference Chair of @CloudExpo & @ThingsExpo, and Editor of SYS-CON Media's CloudComputing BigData & IoT Journals. He holds a BA from Knox College & conducted MBA studies at CSU-East Bay.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


CloudEXPO Stories
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the benefits of the cloud without losing performance as containers become the new paradigm.
In this presentation, you will learn first hand what works and what doesn't while architecting and deploying OpenStack. Some of the topics will include:- best practices for creating repeatable deployments of OpenStack- multi-site considerations- how to customize OpenStack to integrate with your existing systems and security best practices.
In an era of historic innovation fueled by unprecedented access to data and technology, the low cost and risk of entering new markets has leveled the playing field for business. Today, any ambitious innovator can easily introduce a new application or product that can reinvent business models and transform the client experience. In their Day 2 Keynote at 19th Cloud Expo, Mercer Rowe, IBM Vice President of Strategic Alliances, and Raejeanne Skillern, Intel Vice President of Data Center Group and GM, discussed how clients in this new era of innovation can apply data, technology, plus human ingenuity to springboard to advance new business value and opportunities.
The current age of digital transformation means that IT organizations must adapt their toolset to cover all digital experiences, beyond just the end users’. Today’s businesses can no longer focus solely on the digital interactions they manage with employees or customers; they must now contend with non-traditional factors. Whether it's the power of brand to make or break a company, the need to monitor across all locations 24/7, or the ability to proactively resolve issues, companies must adapt to the new world.