Microservices Anti-Patterns

Dallas Monson Agile, Articles, Consulting, Microservices 1 Comment

Microservices? Yeah, you’re doing it wrong.

Microservices is a silver bullet, magic pill, instant fix, and can’t-go-wrong solution to all of software’s problems. In fact, as soon you implement even the basics of microservices all of your dreams come true; you will triple productivity, reach your ideal weight, land your dream job, win the lottery 10 times, and be able to fly, clearly.

While this sounds like a lot of hyperbole wrapped up in some BS, if you have been listening to anything around microservices recently you will most likely have heard something not too far from this exaggerated sentiment – especially if it is coming from sales folks.

As a result of this, you or someone you know will likely have been charged by management to implement a solution in microservices or refactor an existing application to take advantage of microservices to ensure that you get all the magic. With so much overinflation of the truth out there, chances are you may have also implemented a microservices antipattern. These antipatterns are actually more common in the wild than fully functional microservices architectures.

Overview
In this post we will cover the most common antipatterns that I have witnessed in the wild:

Break the Piggy Bank
Everything Micro (Except for the Data)
We are Agile! a.k.a. The Frankenstein

Each one of these results from a common misconception. We will do our best to define these patterns and their symptoms. After each, we will also show a way out of the mess so that you can recover and begin to move towards a better implementation. Let’s get started!

Hello Micronaut

Rik Scarborough Articles, Java, Microservices, Testing Leave a Comment

From some of my previous posts, you can get the idea that I promote the idea of developing maintainable code rapidly. So I was pretty excited when I learned that the same group that was responsible for Grails was working on a similar project for Web Services. Hello, Micronaut.

In this post, I provide an introduction to the Micronaut framework and its features to provide a foundation for you to try it out yourself.

Could the Equifax Hack Have Been Prevented by a Microservices Architecture?

David Pitt Architecture, Articles, DevOps, Java, Microservices, Opinion, Security Leave a Comment

When I heard that the Struts Open Source framework played a role in the recent Equifax hack, I wanted to do some research to understand how it happened. Struts is a commonly-used Java framework that I have applied in the past. And I’m not alone in that: it is reported that in 65% of Fortune 500 companies currently implement Struts in some way.

So, I did a little digging and performed a thought experiment asking myself the following question: “If Equifax had a pure-play Microservices Architecture in place, would it have solved the problem?”

See Keyhole at Nebraska.Code() 2017

Lauren Fournier Bogner Articles, Community, Company News, Educational Event Leave a Comment

Keyhole Software is excited to once again be a Gold sponsor of the Nebraska.Code() Conference. If you have yet to register to attend, use promo code Keyhole10 to receive 10% off of your 2017 conference ticket cost.

The conference will take place this week, Wednesday through Friday, May 17-19. Wednesday will consist of half and full-day workshops, while Thursday and Friday will consist of one-hour breakout sessions.

Keyhole will be giving away a $150 Amazon gift card in a random drawing. Stop by the Keyhole booth on Thursday to enter the drawing, which will take place early Friday afternoon.

Numerous conference sessions will be led by Keyhole Software team members on a myriad of technical topics. Make sure to attend the following Keyhole sessions when setting your own personal conference calendar….

White Paper Published – Microservices: Patterns for Enterprise Agility and Scalability

Keyhole Software Architecture, Articles, Company News, Microservices, Tutorial 4 Comments

We’re excited to announce the release of a new, free white paper on the Microservices software architecture style.

Microservices is an architectural pattern gaining steam in the development community. A Microservices architecture addresses problems that modern enterprises often face, including responding to market demands, handling spikes in traffic, and being tolerant to failure. These benefits are achieved by functionally decomposing a business’ domain into microservices, services that handle only a single responsibility.

In this white paper, we discuss how Microservices came to be, contrasting architecture patterns, features of a Microservices architecture, established patterns, how to get started with Microservices, and suggestions for Microservices adoption.

Download the free Keyhole Software white paper today!