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.
Jan-Joost Bouwman and Mark Heistek, from ING Retail Banking Netherlands, presented at Devopsdays Amsterdam how a CMMI-ITIL organization transitioned to a more agile mindset. Somewhat unusually in this kind of sessions, ING presented quantitative evidence of the improvements, such as a marked increase in the number of changes deployed to production and a decrease of the risk value per change.
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.
At the Agile Governance conference in Amsterdam Jan van Santbrink presented how architecture when used with an agile mindset can play a key role in governance. InfoQ interviewed Jan about why agile and architecture need to collaborate, how architecture can support agile decision taking and the benefits for development of doing architecture.
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.
Hadoop Summit Day One report covers the important trends and changes from last year's summit. It also covers the important announcements of the day in relation to this year's trending topics. This report focuses on the platform specific innovations and announcements and not the broader partner ecosystem, which will be covered in the next few days.
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).
How can we manage and govern multiple agile teams? At the Agile Governance conference in Amsterdam Christoph Johann Stettina presented about agile governance and the role of management. He studied 14 large European organizations on how they apply agile project management methods in IT project portfolios.
Trust is a decision about your investment in the relation says Anko Tijman. Agile governance should be build upon trust. At the Agile Governance conference in Amsterdam Anko Tijman presented being in control through people. Governance is often based on analytical control using structures and models.
Andrew Craddock will give a talk at the Agile Governance conference May 13 in Amsterdam about properly governed Agile projects. InfoQ did an interview with him about what agile governance is and why you need to embed governance practices into your agile development process.
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.