Development and collaboration software vendor Atlassian held its annual developer conference AtlasCamp in Berlin, focusing on the recently launched Atlassian Connect 1.0, the new REST APIs for Confluence and HipChat as well as the JIRA and Confluence Data Center offerings for high availability and performance at scale.
At the Bacon Conference last May, bitly Lead Application Developer Sean O'Connor explained the most relevant lessons bitly developers learned while building a distributed system that handles 6 billions clicks per month.
Managing micro-services means looking after lots of small systems talking to each other and automated provisioning as well as infrastructure automation is crucial, James Lewis states when sharing techniques and practices that have helped him manage the increased operational complexity a microservice architecture gives.
Silk has recently open-sourced a REST framework for Haskell, called "rest". It provides a DSL for defining REST services which can then be run in popular web frameworks such as happstack. This comes with features such as type-safe URLs, abstraction of format-type support, and a clean separation of API specification and business logic.
“I coined the term µServices four years ago defining them as services that always communicate within the same process, without any overhead, as a way to separate these lightweight services from the heavy, costly, and complex services people tended to think about because of the advent of Service Oriented Architectures (SOA)” Peter Kriens recently claimed.
At latest Drupal Conference in Austin, TX, mobile and web development company Lemberg has introduced a native Drupal 8 software development kit. Lemberg's SDK aims at making it easier for developers to handle the communication between a native mobile app and a Drupal website. The SDK is currently available only for iOS and Android, while the Windows Phone version should be coming soon.
The recently released version v1.0.0 of HazelcastMQ adds a Java STOMP client and server implementation as well as an Apache Camel component. HazelcastMQ is a provider of a messaging layer on top of the basic Queue and Topic data structures in Hazelcast, an in-memory data grid. STOMP is the Simple (or Streaming) Text Orientated Messaging Protocol, an interoperable wire format.
3scale launched APITools in the month of April this year targeted at API consumers. InfoQ spoke to 3scale management regarding motivation and underlying technology among other things and walked away with some interesting insights as well as upcoming initiatives to involve the community.
Designing for simple components and systems is key when moving to microservices. The focus is on evolution of components and how we build systems that allow evolution and change, Russ Miles recently stated in an introduction to designing and building microservices.
During the recent GlueCon 2014 conference in Colorado, Tony Tam, the creator of Swagger and CEO of Reverb, gave a well attended talk on Swagger APIs for humans (and robots), where he announced the Swagger 2.0 Working Group and an early version of an online code editor offering a dynamic YAML to Swagger UI conversion.
The Particular Service Platform has four headline components: ServiceMatrix, ServiceInsight, ServicePulse, and the well-respected NServiceBus. Over the next few weeks, we’ll be looking at each in turn starting with ServiceMatrix, their SOA design tool.
There has been significant buzz around microservices lately, enough to generate some hype. After implementing heavy and cumbersome SOA solutions for more than a decade, are microservices the solution the industry has been waiting for? Or, are microservices simpler than monolithic solutions?
According to Gartner’s Yefim V. Natis, VP & Fellow, a new enterprise architectural style is rising these days: Software-Defined Architecture (SDA).
Arnon Rotem-Gal-Oz has written an article following on from other discussions around the term Microservices and whether and how it relates to SOA. According to Arnon, this could be a slippery slope towards the Nonoservices anti-pattern, especially as some people define a Microservice in terms of lines of code.
Using size for defining microservices is useless when determining a service responsibility, Jeppe Cramon states in a series of blog posts explaining his view on microservices and the coupling problems he finds in synchronous two-way communication.