![\"Explaining](\"https:\/\/solutionsreview.com\/cloud-platforms\/files\/2016\/08\/Explaining-the-Cloud-What-the-Heck-is-Microservices-Architecture.png\")
<\/p>\n<\/p>\n
Developers are using Microservices architecture to design and build highly scalable, “lightweight” applications, and while the system may have it’s drawbacks, popularity of microservices has gained momentum over the past several years. This means that you need to know how DevOps are leveraging the architecture to deliver applications in an agile new way.<\/p>\n
Microservices can be defined more by the characteristics of the method of developing software applications, sort of similar to the way you identify blackholes in space; by the behavior of the objects around it. Microservice architecture employs a host\u00a0of independently deployable, small, modular services in which each service runs a unique process and communicates through a defined, lightweight mechanism to serve a business goal. Gartner<\/a>\u00a0inc.\u00a0touches upon the topic\u00a0in their blog post, “Microservices: Building Services with the Guts on the Outside<\/a>“, by\u00a0Gary Olliffe.<\/p>\n “I want to introduce you to what I think is an important clarification of microservice architecture: \u00a0the distinction between simpler \u201cinner architecture\u201d and more complex \u201couter architecture\u201d.\u00a0First, some level-setting. Microservice architectures promise to deliver flexibility and scalability to the development and deployment of service-based applications. But how is that promise delivered? \u00a0In short, by adopting an architecture that allows individual services to be built and deployed independently and dynamically; an architecture that embraces DevOps practices.”<\/p>\n \n “A monolith application is always built as a single, autonomous unit. In a client-server model, the server-side application is a monolith that handles the HTTP requests, executes logic, and retrieves\/updates the data in the underlying database.\u00a0 The problem with a monolithic architecture, though, is that all change cycles usually end up being tied to one another.\u00a0 A modification made to a small section of an application might require building and deploying an entirely new version.\u00a0 If you need to scale specific functions of an application, you may have to scale the entire application instead of just the desired components.\u00a0 This is where creating microservices can come to the rescue.”<\/p>\n More: The difference between Monolithic Architecture and Microservice Architecture<\/a><\/p>\n <\/div><\/a><\/p>\n Microservices architecture is flexible and resilient.\u00a0The services themselves are simple, by focusing on doing only one task\u00a0makes them easier to test. \u00a0Each service can be built with the best suited technologies and tools present at the time, so in the event of an upgrade, developers\u00a0don\u2019t have to be stuck with an early choice of technology for the rest of the project. This allows much more space to move and experiment. The benefits don’t stop there; microservices provide fault isolation so that in the event that\u00a0a service goes down, parts that directly depend on it will leave the other parts\u00a0able to function.<\/p>\n Common drawbacks of the architecture, you’ll hear developers describe on forums like Reddit Microservices<\/a>: That this technology is not for the novice, asserting that substantial DevOps skills are required to make it successful. It’s also commonly mentioned that Microservices creates significant operations overhead.\u00a0In a post<\/a> by\u00a0Benjamin\u00a0Wootton<\/a>,\u00a0CTO of\u00a0Contino consultancy, who specialize in applying DevOps and Continuous Delivery to software delivery projects, Wootton explains that operating and orchestrating all these services can be a daunting task.<\/p>\n “Productizing all of this needs high quality monitoring and operations infrastructure. Keeping an application server running can be a full time job, but we now have to ensure that tens or even hundreds of processes stay up, don’t run out of disk space, don’t deadlock, stay performant.”<\/p>\n Professionals in the space also commonly assert that the architecture makes asynchronicity and testability, challenging.\u00a0Wootton\u00a0warns users:<\/p>\n “Microservices are not a free lunch!\u00a0I am currently involved in architecting a system based around Microservices, and whilst the individual services are very simple, a lot of complexity exists at a higher level level in terms of managing these services and orchestrating business processes throughout them.\u00a0Microservices one of these ideas that are nice in practice, but all manner of complexity comes out when it meets reality.”<\/p>\n By implementing microservices architecture, developers are able to build apps as a host of small, semi-autonomous processes that perform specific tasks and use APIs to communicate with each other. Microservices are gaining popularity because of the easy to use nature, and scalability that the architecture offers.<\/p>\n For more on Microservice, and PaaS vendor news, follow us on Twitter<\/a> and Linkedin<\/a>.<\/p>\n \n","protected":false},"excerpt":{"rendered":" Developers are using Microservices architecture to design and build highly scalable, “lightweight” applications, and while the system may have it’s drawbacks, popularity of microservices has gained momentum over the past several years. This means that you need to know how DevOps are leveraging the architecture to deliver applications in an agile new way. What the […]<\/p>\n","protected":false},"author":29,"featured_media":1227,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[74,42,403,10,410],"acf":[],"yoast_head":"\n
Widget not in any sidebars
Back to our blackhole reasoning, it helps to consider Microservice’s polar opposite: Monolithic Architectural style, to understand the process better. SmartBear<\/a>,\u00a0an organization that\u00a0helps software teams create apps and APIs from code to live, describes Monolithic Architecture in their blog, “What is Microservices Architecture?<\/a>“,\u00a0and how it saves developers a ton of headache.<\/p>\n![\"frontend-microservices-session-state\"](\"https:\/\/solutionsreview.com\/cloud-platforms\/files\/2016\/07\/frontend-microservices-session-state.png\")
<\/p>\n<\/a><\/p>\nThe Perks<\/span><\/h3>\n
Drawbacks<\/h3>\n
Conclusion<\/h3>\n
Widget not in any sidebars
\n