Welcome!

Java IoT Authors: Zakia Bouachraoui, Elizabeth White, Pat Romanski, Liz McMillan, William Schmarzo

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

@DevOpsSummit: Article

SOA or Microservices? | @DevOpsSummit #DevOps #IoT #Docker #Microservices

Some say, microservices is just SOA done right

This is a no-hype, pragmatic post about why I think you should consider architecting your next project the way SOA and/or microservices suggest. No matter if it’s a greenfield approach or if you’re in dire need of refactoring. Please note: considering still keeps open the option of not taking that approach. After reading this, you will have a better idea about whether building multiple small components instead of a single, large component makes sense for your project.

This post assumes that you have experience with software architecture and services (you’ll find some words about my experience on the bottom of this post). I won’t go into the details of Wikipedia’s or Martin Fowler’s definitions per se. Much more I will talk about what microservices and/or SOA could and should do for your project.

Microservices? SOA? Both? None?
I’ll leave it up to you if they are both the same. Some say, microservices is just SOA done right. Some say, microservices has common roots with SOA but is really next-gen and lightweight and less-enterprisey and whatnot.

I don’t stand the slightest chance of resolving this. Therefore, I won’t go with either of them. I’ll go with microsoavices instead. It’s not meant to be funny (in the first place, that is), it’s meant to be a pragmatical phrase that saves me from overhead typing.

The perfect software architecture doesn’t exist
There is no perfect generic software architecture approach but you knew that already. Microsoavices might just not be the perfect fit for your project or even your company. What’s a microsoavice anyway? First and foremost, I’d like to reduce it to two simple key points

  • Fine-grained responsibility
  • Built for fault-tolerance

Those two things are the least common denominator for me on everything you and I already have read about the topic. They should be the basis for any project, no matter if it’s your shiny (shabby?) little garage project or if you’re out for something really big.

Fine-grained responsibility
Microsoavices may be single-task or single domain. Here’s an example for a single-task microsoavice.

Most likely, projects not merely consist of business logic and application domains. There are always some plain utilities involved. I once worked on a project that needed to convert RTF files to HTML. We used a library for that, so it was really easy. On the other hand, updating the library required us to re-deploy all instances of our application. Deployment was automated and we didn’t have to send out floppy-disks with the new versions to our customers but anyway, for a team of three maintaining dozens of instances it required quite some attention.

Wrapping that same library into a stand-alone application that’s listening for incoming HTTP requests was all that was necessary to turn it into a microsoavice (yes, and that final re-deployment of all the instances that changed the internal library call into an external HTTP request). Anyway, from that day on, updating that library was just a matter of re-deploying that single component (as long as the API stayed stable).

Besides single-task microsoavices there’s also more than enough use-cases for covering application domains instead of just single tasks. Take a shopping cart as an example. There are simple functions like

  • Add product to cart
  • Remove product from cart
  • Update product’s quantity in cart

Nobody seriously thinks about creating separate services for those tasks and that’s the reason why it’s as fine-grained as it needs to be (and should be, probably).

Built for fault tolerance
In-process method calls, are replaced with external calls between components. The big difference is that external calls are much more likely to fail. And they will. This requires attention but taking care of it appropriately makes your whole system much more stable and fault-tolerant by design already.

It’s up to you whether you go for a library that handles the issue for you or if you want to take care of it yourself but don’t make the mistake of not taking care. Fault tolerance really is a central issue. Getting it done right early on is the key to succeed with microsoavices.

The problems
Building, deploying and maintaining an ecosystem of many small, independent components poses its own problems. You not only face the problem of fault tolerance, but also the problems of

  • Configuration (where do I reach that service?)
  • Monitoring (what services are available?)
  • Deployment (how many instances are up? on which hosts are they running)
  • Testing (what to do in case of a failing service call?)
  • And quite some more.

Testing and deployment should be taken care of by continuous integration and deployment tools that are available. Monitoring was not there until recently but is already catching up with new products entering the market. Central configuration of a microsoavice environment is probably something that could be solved by using some ESB-like tool.

You see, there seems to be a solution for everything, you might just not be all too happy with them. And I honestly think that we’re not fully there yet when it comes to tooling. The future will bring lots of good tools that make building, deploying and maintaining microsoavices much easier.

The mindset
From my own experience I can say that going down microsoavice lane is not just about all the technical problems. It’s a little bit like the agile thing, which is really also quite a bit about the mindset.

If you are concerned about increased danger of failure because of single failing services, then you probably need to think about it again. If you see how all those small components help you decrease the likeliness of failure, you’re probably settled.

One most important thing not to forget is your developers. Make sure they get the idea of what microsoavices are all about. I will try to cover in a future post, how microsoavices change and improve a developer’s everyday life.

My experience
I have been working as a software developer for about a decade. During that time I worked on all different kinds of projects. I did about 90% web stuff with Java and JavaScript, and also some C#.NET, Visual Basic (pre-dotnet), perl, php, python, etc. I worked several years as a senior lead developer / architect hybrid but also did projects as a one-man-team handling everything from development to deployment and maintainance. Yes, sounds impressive, but, hey, I just did my job.

Looking back, I did some projects which would have really benefitted from doing the microsoavice approach and some others, which surely would have not. And I did one project that was forced into the enteprise-SOA thing in a very dogmatic way, which is why I want to write about the topic pragmatically and from a practical perspective.

Up next
This was just a short introduction to the topic to get your mouth wet. I just touched some keypoints briefly but I will go much more into detail in the posts to follow.

While you’re waiting, why not sharing some of your worst experiences with the topic so far? Tell me about ignorant software architects and blind followers of dogmas, I’m always in for a good laugh.

The post SOA or microservices? (It doesn’t matter a pair of fetid dingo’s kidneys) appeared first on The ruxit blog.

More Stories By Dynatrace Blog

Building a revolutionary approach to software performance monitoring takes an extraordinary team. With decades of combined experience and an impressive history of disruptive innovation, that’s exactly what we ruxit has.

Get to know ruxit, and get to know the future of data analytics.

IoT & Smart Cities Stories
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...