Microservices are valuable, but to break things up properly creating the right boundaries we need to understand our business and its processes Jeppe Cramon stated in a presentation at the Microservices Conference in London.
Udi Dahan describes how looking for highly cohesive, loosely coupled microservices, not within a system but over the enterprise, we can end up with a focus on organising services around business capabilities spanning the whole organisation since this is what the business care about.
The real requirements of a product are not the functions that are needed, or user stories that have to be delivered. It is the possible improvement of performance that customers can get from using the product said Matteo Vaccari. At the XP Days Benelux 2014 conference he facilitated a workshop together with Antonio Carpentieri about defining the value that is needed by customers.
At the Lean Kanban France 2014 conference Bjarte Bogsnes gave a keynote presentation about beyond budgeting. In his presentation he talked about the problems with traditional management and how transparency and self regulating management comes to the rescue, and the principles and practices of beyond budgeting.
When organizations decide to scale agile they can be looking for agile ways to define strategies, manage direction and sustain alignment. Deploying and stay aligned, is today's challenge said Pierre Neis. At the Lean Kanban France 2014 conference Pierre showed how using Hoshin Kanri has helped global players in their lean agile transition.
Kanban is often used to manage work, but the concepts of kanban can also be used to guide a journey of change in an organization. This is a case study of an insurance company that used kanban to get change done to improve visibility and predictability and engaging their people.
Architecture is looking at things in a bigger context, thinking ahead and making decisions. Using their technical and communication skills architects can play a significant role in this by establishing direct contacts with people at different levels in an organisation, Gregor Hohpe said when sharing his experiences from working for Google, and now as Chief IT Architect at Allianz.
Software Development is often considered to be knowledge intensive, therefor organizations look for ways to enable continuous learning. “We need learning organisations and they start with learning individuals” says Marcin Floryan. Individual learning can be difficult and scaling individual learning even more challenging. What can organizations do to become a continuous learning organization?
Chad Fowler, CTO at 6Wunderkinder, the company behind Wunderlist, describes how they went from a large monolithic Rails application and a large monolithic database to a system with many microservices, and the architecture they ended up with. Starting by adding new functionality as services and splitting the large database into smaller databases, they ended up doing a big rewrite of a new system.
Service-Oriented Architecture (SOA) is a very broad term and practically meaningless. Microservices is a subset of SOA with the value being that it allows us to put a label on this useful subset of SOA terminology, Martin Fowler stated in his keynote introducing Microservices when opening the GOTO Berlin Conference 2014.
In stead of feature farming, we need to deliver better outcomes and focus on the business results that we need to deliver. Measurements should provide insight into the outcomes because that is what is important. The Mobius loop can be used to define appropriate measurements.
After gestating for more than a year on GitHub, the project Streams has now been adopted by WHATWG in an effort to standardize a web streaming API. The project is led by Domenic Denicola, the man that started the work on Promises, currently part of the upcoming ECMAScript 6.
W3C published a new version of the HTML5 Differences from HTML4 working draft. The latest version describes the differences of W3C HTML5 and HTML4, and a comparison between WHATWG HTML and HTML4 is no longer covered.
The Apache Camel team recently released version 2.14, their 66th release. Camel is an open-source integration framework that provides components based on the popular enterprise integration patterns. It allows an application to define route and mediation rules in many domain-specific languages (DSLs), for example with Java, XML, Groovy and Scala.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.