The importance of microservices and integration as we get closer to 2017 cannot be overstated. Survey results show that the majority of companies are converting to microservice-oriented architecture to create more integration.

This represents a major change in the way that many companies operate. Here are 5 pieces written about microservices and integration and their advantages.


WhyYouNeedIntegrationPlatform

Why do you need an
integration platform?

Download our resource to learn more

Microservices as an Evolutionary Architecture by ThoughtWorks

The microservice architectural style is taking the world by storm. Last March, O’Reilly hosted their first Software Architecture Conference, and a huge percentage of the abstracts the program committee received touched on some aspect of microservices. Why is this architectural style suddenly all the rage?

Microservices are the first post DevOps revolution architectural style, the first to fully embrace the engineering practices of Continuous Delivery. It is also an example of an evolutionary architecture, which supports incremental non-breaking change as a first principle along multiple dimensions at the structural level of the application. However, it is only one of group of architectures that support certain evolutionary behaviors. This article investigates some characteristics and principles of this family of architectural style.

Read full article >>


Innovate or Die: The Rise of Microservices by Sequoia Capital

The concept of microservices is not new. Google Inc., Amazon.com Inc. and Facebook Inc. have been running microservices for over a decade. In fact, every time you search for a term on Google, it calls out to roughly 70 microservices before it returns your results.

Enterprises tried to replicate this with an approach called “service-oriented-architecture” that largely failed because the right building blocks for mass adoption were not yet in place. The three main building blocks that were needed are now established.

Read full article >>


Navigating legacy: Charting the course to business value by Deloitte

In the 2015 global CIO survey, we showed you a map for creating CIO legacy. We defined “legacy” as how technology leaders deliver lasting value to their organizations. A key finding was that effective CIOs add value in three distinct ways based on the needs of the business. Trusted operators ensure operational excellence, change instigators enable large business transformations, and business co-creators focus on revenue and growth. (See sidebar “CIO legacy pattern types” for more detail.) We also described how CIOs can diagnose their situation by recognizing their current pattern and identifying which pattern they should move toward to better meet the needs of their businesses.

This lens—the needs of the business—determines which pattern will most effectively enable CIOs to add lasting value by preparing themselves and developing the people and processes needed to deliver that value into the future. From the 2015 survey, we concluded that no pattern type is better than any other; indeed, successful CIOs can, and should,navigate from one pattern to another based on shifting business needs.

Read full article >>


The microservices substrate – NetflixOSS, Spring Cloud Services, and Pivotal Cloud Foundry by Pivotal

Microservices aim to bring an unprecedented amount of agility to complex, distributed systems: each service can update at will, always getting the latest innovations and functionality into production. That said, this amount of rapidly moving parts brings a whole new set of management and operations needs to the forefront, not to mention simple acts like looking up a service to use.

Read full article >>


Why The Next Great SaaS Company Will Look Nothing Like Salesforce by Aaref Hilaly

At big companies, integration is the ugly step-child of any product roadmap: everyone wants it to work, but no one wants to work on it [1]. Start ups have capitalized on that by creating high performance, scalable integrations, solving hard technical problems like how to sync without putting excessive load on the underlying system. Entire companies, such as Okta for single sign-on or Segment for analytics, are now built on integration alone [2]. But most new applications use integration to gather, organize, and analyze data. They win the hearts of their users through great design. That’s no small challenge, given growing data sets, shrinking screen sizes, and ever shorter attention spans, which is why design has become a huge differentiator.

Read full article >>


Are you interested in diving deeper into a microservice-oriented architecture? Contact Azuqua today for a demo of our integration platform that allows you to rapidly create and connect microservices.