In a recent article Martin Fowler tries to answer the question about when to consider using microservices, hoping that developers understand that there is an inherent complexity involved in making such an architectural change. Sometimes staying with a well-designed monolith may be more appropriate.
Under the name of Project Oxford, Microsoft has made available a set of RESTful APIs that aim to make it possible for developers to build apps that feature face recognition, speech processing, and other machine learning algorithms. Part of the Azure portfolio, the new APIs are currently in beta and free to use up to 5,000 call per month.
Standardizing on common models for business objects that are exchanged within an enterprise, e.g. Customer, Order and Product together with the attributes and associations they have, might seem compelling but for Stefan Tilkov this creation of Canonical Data Models (CDMs) is a horrible idea which he strongly advices against.
Recently Adrian Cockcroft gave an interview to ActiveState's John Wetherill about microservices. In it he talks about how polyglot fits into microservices and the impact on him when he head that companies such as Target and Macy's, as well as Homeland Security had adopted that architectural approach.
AnyPresence, one of the leading MBaaS players has launched JustAPIs, a platform for building and deploying RESTful APIs.
A service is a logical construct owning a business capability and made up of internal autonomous components or microservices that together fulfil the responsibilities of the service, Jeppe Cramon suggests continuing a previous series of blog posts clarifying his view on building services around business capabilities and bounded contexts.
Popular configuration mechanisms like conf.d pose multiple problems when trying to converge system configuration using configuration management tools. Ish-Shalom proposes five design principles for configuration that prevent those problems. The core ideas being the use of a configuration API and the separation of configurations based on the type of system updates they require.
The Yelp engineering team have stated that moving to a service-oriented architecture has allowed them to scale their development process and maintain a rapid pace of software delivery as the team and codebase has grown. This has been achieved by focusing on distributed systems education, creating a set of basic service design principles and implementing a supporting infrastructure.
Business process management software provider Effektif today announced the open sourcing of their workflow engine. The new model allows developers to include Effektif workflows from within their applications via Java and REST APIs
The assumption that a large system must have a single environment, often with a one-to-one mapping between a project’s scope and the system built are challenged today Stefan Tilkov explains when looking into ways to split a large system into smaller parts and comparing the characteristics of systems, applications and microservices.
Mark Little discusses the anatomy of microservices, how they can be used, and why you may want to temper your enthusiasm to get them to production.
Udi Dahan, a SOA consultant, held the presentation Finding Service Boundaries – Illustrated in Healthcare at NDC London 2014, providing advice on establishing the service boundaries in a SOA or microservice architecture.
As computation and storage are cheap today, keeping immutable copies of lots of data becomes affordable, and by doing this, the coordination challenges can be reduced.
MuleSoft has announced this month the release of ESB 3.6 runtime, improvements to Anypoint Studio and the Anypoint Platform for Mobile to support mobile application development.
Amazon announced the launch of Amazon WorkMail, a managed business email and calendaring service.