|By Ruxit Blog||
|October 25, 2016 06:00 AM EDT||
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.
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.
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.
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.
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.
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.
SYS-CON Events announced today that Interface Masters Technologies, a leader in Network Visibility and Uptime Solutions, will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Interface Masters Technologies is a leading vendor in the network monitoring and high speed networking markets. Based in the heart of Silicon Valley, Interface Masters' expertise lies in Gigabit, 10 Gigabit and 40 Gigabit Eth...
Oct. 25, 2016 05:45 AM EDT Reads: 3,345
We are reaching the end of the beginning with WebRTC, and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will w...
Oct. 25, 2016 05:30 AM EDT Reads: 3,368
As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and microservices. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your conta...
Oct. 25, 2016 05:30 AM EDT Reads: 1,515
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
Oct. 25, 2016 05:15 AM EDT Reads: 1,992
DevOps theory promotes a culture of continuous improvement built on collaboration, empowerment, systems thinking, and feedback loops. But how do you collaborate effectively across the traditional silos? How can you make decisions without system-wide visibility? How can you see the whole system when it is spread across teams and locations? How do you close feedback loops across teams and activities delivering complex multi-tier, cloud, container, serverless, and/or API-based services?
Oct. 25, 2016 04:45 AM EDT Reads: 1,084
SYS-CON Media announced today that @WebRTCSummit Blog, the largest WebRTC resource in the world, has been launched. @WebRTCSummit Blog offers top articles, news stories, and blog posts from the world's well-known experts and guarantees better exposure for its authors than any other publication. @WebRTCSummit Blog can be bookmarked ▸ Here @WebRTCSummit conference site can be bookmarked ▸ Here
Oct. 25, 2016 04:30 AM EDT Reads: 9,701
You have great SaaS business app ideas. You want to turn your idea quickly into a functional and engaging proof of concept. You need to be able to modify it to meet customers' needs, and you need to deliver a complete and secure SaaS application. How could you achieve all the above and yet avoid unforeseen IT requirements that add unnecessary cost and complexity? You also want your app to be responsive in any device at any time. In his session at 19th Cloud Expo, Mark Allen, General Manager of...
Oct. 25, 2016 04:15 AM EDT Reads: 947
One of biggest questions about Big Data is “How do we harness all that information for business use quickly and effectively?” Geographic Information Systems (GIS) or spatial technology is about more than making maps, but adding critical context and meaning to data of all types, coming from all different channels – even sensors. In his session at @ThingsExpo, William (Bill) Meehan, director of utility solutions for Esri, will take a closer look at the current state of spatial technology and ar...
Oct. 25, 2016 04:15 AM EDT Reads: 1,738
SYS-CON Events announced today that Streamlyzer will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Streamlyzer is a powerful analytics for video streaming service that enables video streaming providers to monitor and analyze QoE (Quality-of-Experience) from end-user devices in real time.
Oct. 25, 2016 04:15 AM EDT Reads: 1,008
SYS-CON Events announced today that SoftNet Solutions will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. SoftNet Solutions specializes in Enterprise Solutions for Hadoop and Big Data. It offers customers the most open, robust, and value-conscious portfolio of solutions, services, and tools for the shortest route to success with Big Data. The unique differentiator is the ability to architect and ...
Oct. 25, 2016 04:00 AM EDT Reads: 962
The IoT industry is now at a crossroads, between the fast-paced innovation of technologies and the pending mass adoption by global enterprises. The complexity of combining rapidly evolving technologies and the need to establish practices for market acceleration pose a strong challenge to global enterprises as well as IoT vendors. In his session at @ThingsExpo, Clark Smith, senior product manager for Numerex, will discuss how Numerex, as an experienced, established IoT provider, has embraced a ...
Oct. 25, 2016 03:45 AM EDT Reads: 1,123
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his session at @DevOpsSummit 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will show how customers are able to achieve a level of transparency that enables everyon...
Oct. 25, 2016 03:30 AM EDT Reads: 1,306
Today every business relies on software to drive the innovation necessary for a competitive edge in the Application Economy. This is why collaboration between development and operations, or DevOps, has become IT’s number one priority. Whether you are in Dev or Ops, understanding how to implement a DevOps strategy can deliver faster development cycles, improved software quality, reduced deployment times and overall better experiences for your customers.
Oct. 25, 2016 03:30 AM EDT Reads: 918
Cloud based infrastructure deployment is becoming more and more appealing to customers, from Fortune 500 companies to SMEs due to its pay-as-you-go model. Enterprise storage vendors are able to reach out to these customers by integrating in cloud based deployments; this needs adaptability and interoperability of the products confirming to cloud standards such as OpenStack, CloudStack, or Azure. As compared to off the shelf commodity storage, enterprise storages by its reliability, high-availabil...
Oct. 25, 2016 03:15 AM EDT Reads: 1,154
Donna Yasay, President of HomeGrid Forum, today discussed with a panel of technology peers how certification programs are at the forefront of interoperability, and the answer for vendors looking to keep up with today's growing industry for smart home innovation. "To ensure multi-vendor interoperability, accredited industry certification programs should be used for every product to provide credibility and quality assurance for retail and carrier based customers looking to add ever increasing num...
Oct. 25, 2016 02:00 AM EDT Reads: 612