Preparing for problems like partial failure is the best thing you can do when working with distributed systems, Vaughn Vernon explains in a conversation with InfoQ and refers to a blog post by Jeff Hodges noting its down-to-earth approach and practical advices e.g. designing for partial availability, and using capped exponential back off to restore full operation when dependencies are unavailable.
Redfish 1.0 is defined as a standard and a RESTful API for the management of scale-out commodity servers. Although it was created with the current needs of scalable architectures in mind, Redfish can be used for the management or the integration of the older platforms and their tool chains.
Intel has introduced a new feature for its Integrated Native Development Experience (INDE) called Multi-OS Engine that aims to make it easier for Java developers to port their Android apps to the iOS platform.
REST and hypermedia has a lot of benefits but they significantly complicates building both the client and the server API, thus useful only in some scenarios Jimmy Bogard states in a series of blog posts highlighting what’s needed to get a full hypermedia solution from server to client including choosing a hypermedia-rich media type.
Reuse has been a watch word for almost everything that has happened in system development during the last thirty years, but reuse is like cyanide; in really small portions it can be healthy, using it too much it starts doing a lot of damage, Udi Dahan claimed in his presentation giving a different perspective on business logic at this year’s DDD Exchange conference in London.
At QCon New York 2015, David Fullerton presented a deep-dive into the monolithic C# / MS SQL architecture that powers the Stack Overflow website, which handles over 4 billion requests per month. Fullerton argued that by focusing on performance, scalability was included ‘almost for free’; and that by minimising the number of external application services, the need to pay ‘SOA tax’ has been avoided.
During the last months Martin Fowler among others have claimed that a microservices architecture should always start with a monolith, but Stefan Tilkov is convinced this is wrong, building a well-structured monolith with cleanly separated modules that later may be pulled apart into microservices is extremely hard, if not impossible in most cases.
Parse has announced its new Schema API, which allows to programmatically manipulate the database schema used by an app, and the Parse API Console, which aims to make it easier to use Parse REST API without writing any code.
At WSO2Con EU 2015, WSO2 has announced API Cloud and App Cloud, two complete solutions for managing APIs and respectively enterprise applications throughout their lifecycle.
With GCM 3.0, Google has attempted to simplify the registration process and to make their cloud notification system work similarly on Android, iOS and Chrome. There is a new topic group and a messaging diagnostic tool.
Last month, Teamleader won the HenQ award of the Boost competition at The Next Web Europe 2015 in Amsterdam, Netherlands. Benny Waelput from Teamleader discusses about the present and future of CRM systems.
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.