Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Carmen Gonzalez, Elizabeth White, Jason Bloomberg

Related Topics: Microservices Expo, Containers Expo Blog, @CloudExpo, @DevOpsSummit

Microservices Expo: Blog Post

PaaS and #Microservices: Part 6 By @bcferrycoder | @DevOpsSummit #DevOps #PaaS

We have a long way to go before many/most medium & large enterprises are able to achieve the benefits promised by microservices

This is the final installment of the six-part series Microservices and PaaS.

It seems like forever since I attended Adrian Cockroft's meetup focusing on microservices. It's actually only been a couple of months, but much has happened since then: countless articles, meetups, and conference sessions focusing on microservices have been delivered, many meetings and design efforts at companies moving towards a microservices-based approach have been endured, and five installments of this blog series have been written.

There's no doubt that microservices, like containerization and DevOps, is a trending topic these days. But this raises the question: How many enterprise organizations are actually using microservices architectures in production?

In spite of all the trending interest, the buzz, the hype, the articles, the sessions, the meetings, I submit that the answer is effectively...none are.

I say this, not based on costly analyst research, but from talking to literally hundreds of enterprise IT folks including developers, managers, ops people, sysadmins, architects, marketeers, and PR people, across a wide swath of industries. Based on this informal sampling, I conclude that the percentage of enterprises that have made any significant headway with microservices can reasonably be rounded down to 0%.

Heck, I recently talked to a couple of major enterprises who still have Windows XP servers sitting under their POS system in their retail outlets. Every evening, after the store closes, these servers dial home - yes, using a modem - and batch-transfer the day's transactions. I'm talking about well-known international brands here, companies that you and I and your friends and my friends have probably patronized in the last few weeks.

And at VMworld two months ago, a conference that's smack-dab in the middle of enterprise cloud technology, there wasn't a single session abstract (among hundreds) that even mentioned microservices.

While I agree with Adrian, who said at the microservices meetup that "2014 is the year that the enterprise finally gets the cloud," I would argue that 2014 is not that year that the enterprise finally gets microservices. That's still a ways off.

Don't get me wrong: microservices is certainly a significant trend these days, and many forward-thinking organizations are looking at adopting a microservices architecture, but we have a long way to go before many/most medium and large enterprises are able to achieve the benefits promised by microservices.

Action Plan
Get Started Now
I've rambled enough. It's time to see all this in practice. A natural first step in building microservices is to get the toolset in place. Stackato is a natural: it provides most of the features and capabilities discussed in this series, and is incredibly easy to set up and use. In fact you can get Stackato running in less time that it took you to read this article.

Check it out: download Stackato now, and see for yourself how simple it is to get a scalable, microservices platform in place, with powerful features such as scaling, load balancing, monitoring, logging, rollback, single signon, and more, instantly available.

What's Better than Best Practices?
I want to close by saying that the patterns and advice presented in this series are not meant to be construed as "best practices" by any stretch. Frankly, I don't particularly like the phrase "Best Practices" for a number of reasons. The term "Best" implies there are no better practices. But practices and technologies are always evolving. Adopting "Best Practices" can actually stifle progress and encourage complacency. Furthermore, there are oftentimes when "Best Practices" aren't really best for the situation at hand. Consider the well-known "DRY" (Don't Repeat Yourself) principle, a best practice that at times isn't really always best practice (for example: it's occasionally better to repeat code across multiple microservices instead of creating the additional complexity to abstract it). Finally, Best Practices might work for a particular team and a particular project, but adapting these practices to another team/project might be like fitting a round peg in a square hole, and be more costly than coming up with new, customized practices.

What's better than Best Practices? Why, No Practices of course! By definition, Best Practices require work: to learn, evangelize, educate, and adopt. But there's a better approach: No Practices. That's where PaaS comes in. Instead of investing in "Best Practices" to scale, or monitor, or rollback, or secure your applications, save the investment and use the tooling instead, which has many of these practices built-in.

That is, let Stackato do your practicing for you. This allows you, your developers and ops teams, and your organization to perform!

The post Microservices and PaaS - Part VI appeared first on ActiveState.

More Stories By John Wetherill

Originally from Canada, John has spent much of his career designing and building software at a handful of startups, at Sun Microsystems, NeXT Inc., and more recently in the smart grid and energy space. His biggest passion is for developer tools, or more generally any tool, language, process, or system that improves developer productivity and quality of life. Without question, Stackato is one such tool and the reason why he is here. No stranger to technology evangelism, John spent several years in the late 1990's on Sun's Technology Evangelism Team spreading the Java Gospel across the globe and focusing on the prolific number of Java technologies. Now John is now returning to his roots, as a technology evangelist working for a Canadian company, albeit remotely from Santa Cruz.

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.


Microservices Articles
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 bene...
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, will discuss why containers should be paired with new architectural practices such as microservices ra...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin, ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...