Microservices has a very long history, not as short as many believe. Neither was SOA invented in the 90s. We have been working with the core ideas behind services for five decades, Greg Young explained at the recent Microservices Conference in London, during his presentation on working with microservices.
Developers attracted to the Azure Service Bus Relay for its ability to expose web services on internal networks to Internet-facing consumers have had, until recently, only one way to build such services: WCF. Using a just-released public preview called Azure Relay Hybrid Connections, developers may now use any Web socket friendly platform to connect local services to this cloud-based broker.
GitHub recently introduced at their Github Universe conference the alpha release of their new API, written in Facebook’s GraphQL (a query language that allows for self-service API contracts). GitHub writes in its engineering blog that its main reason for switching API paradigms is lack of scalability with their existing RESTful contracts.
Sean Kelly, a Principal Engineer at Komad, has written about his experiences around microservices and five "truths" which developers believe microservices will bring to their architectures, applications and teams, but which, in his view, are not always the case.
ThoughtWorks director Neal Ford argued in a recent talk that organizations transition more easily from a monolithic architecture to a service-based architecture than to a microservices architecture. Ford spoke at UberConf 2016 about service-based architecture, a middle ground between service-oriented architecture and microservices.
Confluent Enterprise latest version supports multi-datacenter replication, automatic data balancing, and cloud migration capability. Confluent, provider of the Apache Kafka based streaming platform, announced last week the new features for Confluent Enterprise, to help build streaming data pipelines and develop stream processing applications.
Yahoo! has made available Pulsar, their publish-subscribe messaging platform used internally in production by several services.
Moving towards microservices means moving towards distributed systems where you have to deal with latency, authorization and authentication, and messages that do not arrive, argues Sander Hoogendoorn. With microservices you can break down large systems into smaller components to regain control over the architecture.
Almost five years in the making, Dropwizard's Java RESTful Web Service framework version 1.0.0 offers a host of new features including Java 8, Http/2 and Scala support, and the latest versions of supporting Java APIs.
Increasingly, software developers have the ability to not only maintain and architect code, but extend their expertise to providing direction to the business. By using domain driven design, developers can discover customer behaviors and recommend practices that change the nature of the business.
We live in a distributed world, but that doesn’t mean we have to tackle every single problem that comes along with that. We only need to tackle those that really need to be solved; develop a sense of where value lies in your business and where it’s reasonable to take risks. This will make building distributed systems much easier, Camille Fournier claimed, when interviewed by Stefan Tilkov.
On July 15th, Microsoft announced the Azure Premium Messaging service has reached General Availability (GA). Premium Messaging targets customers who would like more predictable messaging performance. InfoQ reached out to Dan Rosanova, Principal Program Manager on the Azure Service Bus team for additional insight into this milestone.
In a recent blog post, Uber engineer Emily Reinhold described how they broke a monolithic API into a modular, flexible microservice architecture. She highlighted a few key design and architectural choices that were key to Uber’s migration effort.
WSO2 MSF4J 2.0 has added support for Spring, Swagger definition generation, ExceptionMapper and StreamingOutput.
Microsoft has published their guidance for creating “RESTful” APIs. Roy Fielding calls them HTTP APIs that have little to do with REST.