Welcome!

Microservices Expo Authors: Jason Bloomberg, Elizabeth White, Pat Romanski, Mehdi Daoudi, Liz McMillan

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

Microservices Expo: Blog Post

PaaS and #Microservices By @bcferrycoder | @DevOpsSummit #DevOps #PaaS

Part 5 - Advice for individuals, teams, and organizations considering a move to microservices

In the first four parts of this series I presented an introduction to microservices along with a handful of emerging microservices patterns, and a discussion of some of the downsides and challenges to using microservices. The most recent installment of this series looked at ten ways that PaaS facilitates microservices development and adoption.

In this post I'll cover some words of wisdom, advice intended for individuals, teams, and organizations considering a move to microservices. I've gleaned this advice from the various articles and meetups mentioned above, from dozens of discussions with architects and developers at a handful of organizations who are moving forward with microservices, as well as from my experience building a couple microservices-based systems before microservices was a thing.

Words to the Wise / Words to the Weary
Start small, move fast
Don't expect to "pull a Netflix." What I mean by this is that you throw millions of dollars and buildings - full of smart engineers and architects, with buy-in from the top of the organization, at a rapid corporate-wide metamorphoses from monolithic apps to microservices apps. That's just not realistic for most organizations today. Dramatic changes to the org-chart are almost impossible. Change needs to be small, with minimal investment, and rapid results. With enough measurable success, the slow transition to a microservices-based approach is more within reach.

Choose the right project
Ideally, for your first foray into microservices, choose a project with some of these characteristics:

  • Short-lived
  • Internal
  • Non-production
  • Non-mission critical
  • Small
  • Greenfield, if possible

By focusing on these types of projects you minimize risk while you get the tooling, the process (more accurately, lack of process), and knowledge in place as a foundation for further microservices efforts.

Consider hackathons and lab projects
Taking the lead from Mozilla, consider lab projects as the first steps into microservices. Hackathons and developer contests are particularly well suited. These are short-lived, with participation from passionate and energetic early-adopter-type developers who like to experiment.

Eliminate IT barriers
I can't emphasize this enough: Go to any lengths to eliminate any IT barriers currently impeding app development. Do not, I repeat, DO NOT force a developer to submit a service ticket to provision a resource (VM, data service...). Doing so defeats many of the advantages of microservices and maintains the destructive hierarchy that commonly exists between developers and IT.

However, many organizations might find that disrupting their current ticket-based process to obtain resources is too much of a stretch. If so, find another way. Use an external cloud, such as AWS or Rackspace or HP Helion Public Cloud, for early microservices development. Or, if that's not permissible, build up three Linux PCs and put them under someone's desk. I'm serious here - with today's modern tooling (read PaaS) it's trivial to build a fully functional cloud out of a handful of PCs and with the same tooling; it's equally trivial to move a complex microservices-based application from an under-the-desk cluster to an enterprise data center once the app is ready for prime-time. The point is, go to almost any lengths to make sure there's no ticketing system or other process to interfere.

Allow devs to push to production
A developer who can push to prod is often empowered, and incented to produce higher quality code. This has countless advantages, probably the most significant of which is improved employee retention.

Be ready to throw it out
Do not overthink the early microservices you build. You can easily get mired in the weeds, designing naming schemes, service discovery mechanisms, and inter-service communication protocols. Instead of all that, just roll up your sleeves and dive right in. Build a handful of small microservices and be prepared to rewrite them. One major advantage of building isolated independent microservices is that it can be rewritten rapidly. Take advantage of this.

Identify internal proponents early
Not everybody will be on board with microservices from the start. But some will, and it's helpful to identify these folks as they'll be invaluable for a wider drive to microservices in the future.

Quantify success
The success of a technology change is meaningless and wasted if the benefits are not measurable or measured. Identify a handful of metrics that you can quantify, metrics that microservices will improve. Here are some examples:

  • How long does it take to push out a new feature?
  • How many service desk tickets are required to build a new app?
  • How many days/weeks does it take to onboard a new developer?

Come up with your own, and track them, with the goal of demonstrating the improvements that microservices bring to the table.

Scale from day one
Scaling is an important motivator for moving to cloud computing, and you should be able to scale microservices effortlessly. Make sure the tooling is in place to instantly, automatically, and elastically scale your microservices in response to system load.

Monitor from day one
Similarly, it's important to monitor the overall operation of the system and each microservice that's part of the system. Wire in monitoring tools to each microservice you build before you even write a single line of code for the microservice. Monitoring should not incur additional design and implementation overhead - it must be built into the platform.

Automate everywhere
As discussed previously, eliminate, as much as possible, any need for human intervention for a microservices operation. Almost everything should be automated. This includes monitoring, scaling, logging, rollback, failure detection, testing, and deployment. Again, the right tooling is essential here.

Explore toolsets, understand patterns
The use of microservices is evolving fast, but some established patterns are emerging now, and will continue to emerge. Keep your eye on these, and experiment with them. Learn about ways to support graceful degradation and fault tolerance. Get a handle on the circuit breaker pattern, and explore the Netflix tools that they have generously made freely available. Tools like Chaos Monkey and Hystrix are worth looking at, and possibly adopting. Additionally, it's helpful to understand containerization, and especially recognize the limitations of containers for cloud application development.

And definitely, get a solid grasp of Platform-as-a-Service, the essential foundation for serious and successful microservices deployment.

Expect to fail
Failure is okay. At least, with a small targeted non-mission-critical microservice, failure is okay (and that's kind of the whole point). Learn from the failures, keep calm, and carry on.

Step away from the infrastructure
Do not build anything that's tied to a particular infrastructure. For example, if you do decide to deploy a microservice to AWS, don't hard-wire the microservice to use AWS APIs and facilities. Instead write to an abstraction layer (read PaaS) so that the microservice can be moved to any cloud at any time in the development and delivery cycle.

Just as important, don't get mired in the plumbing. Get out of the IaaS weeds. Allow the PaaS to take care of the underlying details so you can focus on what's important: the functionality, the interface, and the service level agreements.

Determine where you're using Microservices today
You might already be using microservices, at least as a consumer. Do you use Google's geocoding API to convert addresses to locations, or Twilio to send text messages, or Weather Underground to determine weather conditions at your customer location? These external services can be considered microservices, in the sense that they're isolated and loosely coupled from your application codebase, and they can evolve independently.

By looking at places you're using external microservices, you will be able to identify functionality of your existing internal applications that can be split off into microservices, leveraging all the power of microservices in a small, contained service. Again, take small steps.

Use the right PaaS for the job
Look carefully at the license agreements for the tools and services you adopt. Some PaaS offerings, for example, base their licensing costs on number of applications (microservices) deployed to the PaaS. This model is an impediment to a successful microservices adoption since a penalty is incurred for each additional service that's deployed. Others, like Stackato, use a memory model where license fees (if any) are charged based on the overall amount of memory making up a PaaS cluster. The memory pricing model makes much more sense for a microservices deployment: you can construct your application from as many microservices as you like, without incurring additional cost for each individual microservice, other than the memory it consumes.

Get started now
I recommend you get your feet wet now, by downloading the latest Stackato Micro Cloud from ActiveState, deploying a simple service, and discovering the many features of PaaS that ease the journey from a monolithic to microservices approach.

The post Microservices and PaaS - Part V 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.


@MicroservicesExpo Stories
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.
Leading companies, from the Global Fortune 500 to the smallest companies, are adopting hybrid cloud as the path to business advantage. Hybrid cloud depends on cloud services and on-premises infrastructure working in unison. Successful implementations require new levels of data mobility, enabled by an automated and seamless flow across on-premises and cloud resources. In his general session at 21st Cloud Expo, Greg Tevis, an IBM Storage Software Technical Strategist and Customer Solution Architec...
Many organizations adopt DevOps to reduce cycle times and deliver software faster; some take on DevOps to drive higher quality and better end-user experience; others look to DevOps for a clearer line-of-sight to customers to drive better business impacts. In truth, these three foundations go together. In this power panel at @DevOpsSummit 21st Cloud Expo, moderated by DevOps Conference Co-Chair Andi Mann, industry experts will discuss how leading organizations build application success from all...
The last two years has seen discussions about cloud computing evolve from the public / private / hybrid split to the reality that most enterprises will be creating a complex, multi-cloud strategy. Companies are wary of committing all of their resources to a single cloud, and instead are choosing to spread the risk – and the benefits – of cloud computing across multiple providers and internal infrastructures, as they follow their business needs. Will this approach be successful? How large is the ...
‘Trend’ is a pretty common business term, but its definition tends to vary by industry. In performance monitoring, trend, or trend shift, is a key metric that is used to indicate change. Change is inevitable. Today’s websites must frequently update and change to keep up with competition and attract new users, but such changes can have a negative impact on the user experience if not managed properly. The dynamic nature of the Internet makes it necessary to constantly monitor different metrics. O...
Enterprises are moving to the cloud faster than most of us in security expected. CIOs are going from 0 to 100 in cloud adoption and leaving security teams in the dust. Once cloud is part of an enterprise stack, it’s unclear who has responsibility for the protection of applications, services, and data. When cloud breaches occur, whether active compromise or a publicly accessible database, the blame must fall on both service providers and users. In his session at 21st Cloud Expo, Ben Johnson, C...
21st International Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Me...
Today companies are looking to achieve cloud-first digital agility to reduce time-to-market, optimize utilization of resources, and rapidly deliver disruptive business solutions. However, leveraging the benefits of cloud deployments can be complicated for companies with extensive legacy computing environments. In his session at 21st Cloud Expo, Craig Sproule, founder and CEO of Metavine, will outline the challenges enterprises face in migrating legacy solutions to the cloud. He will also prese...
Most of the time there is a lot of work involved to move to the cloud, and most of that isn't really related to AWS or Azure or Google Cloud. Before we talk about public cloud vendors and DevOps tools, there are usually several technical and non-technical challenges that are connected to it and that every company needs to solve to move to the cloud. In his session at 21st Cloud Expo, Stefano Bellasio, CEO and founder of Cloud Academy Inc., will discuss what the tools, disciplines, and cultural...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
With the rise of DevOps, containers are at the brink of becoming a pervasive technology in Enterprise IT to accelerate application delivery for the business. When it comes to adopting containers in the enterprise, security is the highest adoption barrier. Is your organization ready to address the security risks with containers for your DevOps environment? In his session at @DevOpsSummit at 21st Cloud Expo, Chris Van Tuin, Chief Technologist, NA West at Red Hat, will discuss: The top security r...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
The nature of the technology business is forward-thinking. It focuses on the future and what’s coming next. Innovations and creativity in our world of software development strive to improve the status quo and increase customer satisfaction through speed and increased connectivity. Yet, while it's exciting to see enterprises embrace new ways of thinking and advance their processes with cutting edge technology, it rarely happens rapidly or even simultaneously across all industries.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
"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.
One of the biggest challenges with adopting a DevOps mentality is: new applications are easily adapted to cloud-native, microservice-based, or containerized architectures - they can be built for them - but old applications need complex refactoring. On the other hand, these new technologies can require relearning or adapting new, oftentimes more complex, methodologies and tools to be ready for production. In his general session at @DevOpsSummit at 20th Cloud Expo, Chris Brown, Solutions Marketi...
DevOps at Cloud Expo – being held October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real r...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
"When we talk about cloud without compromise what we're talking about is that when people think about 'I need the flexibility of the cloud' - it's the ability to create applications and run them in a cloud environment that's far more flexible,” explained Matthew Finnie, CTO of Interoute, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.