# Finn.no's architecture summit focused on breaking up its iAD monolith into microservices

DevFeed: [Finn.no's architecture summit focused on breaking up its iAD monolith into microservices](<https://devfeed.tech/articles/finn-no-wanted-to-split-up-their-monolith-you-won-t-believe-what-happens-next-31989.md>)

Original publisher: [Read original article](<https://tech.finn.no2015/02/10/summit/>)

Author: Audun Fauchald Strand

Published: 2015-02-10T11:00:00Z

Content type: article

Language: en

Sources: [Finn.no](<https://devfeed.tech/sources/finn-no.md>)

Topics: [microservices architecture](<https://devfeed.tech/topics/microservices-architecture.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Domain-driven design (DDD)](<https://devfeed.tech/topics/domain-driven-design.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [RxJava](<https://devfeed.tech/topics/rxjava.md>), [reactive](<https://devfeed.tech/topics/reactive.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [legacy](<https://devfeed.tech/topics/legacy.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [development](<https://devfeed.tech/tags/development.md>), [domain-driven-design](<https://devfeed.tech/tags/domain-driven-design.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [microservices-architecture](<https://devfeed.tech/tags/microservices-architecture.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [reactive](<https://devfeed.tech/tags/reactive.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [rxjava](<https://devfeed.tech/tags/rxjava.md>)

## AI overview

Finn.no organized a two-day architecture summit to coordinate its development teams around a microservices architecture after breaking up the iAD monolith. The program covered domain-driven design, event-driven architecture, CQRS, service properties, and implementation examples using Node.js, RxJava, and Reactive Streams.

## Source excerpt

After working several years with (successfully) breaking up the legacy monolith, called iAD, Finn.no wanted to add structure to this process, and make sure that all 20 development teams work towards the same target. The target is a microservices architecture with small-ish autonomous services, owning their own data. With that in mind we arranged our own two-day architecture summit for all Lead Developers, with a combination of external and internal presenters. The focus was on microservices, domain driven design, event driven architectures and modern programming techniques. We started off the first day with a long session. Finn.no's Chief Enterprise Architect Sebastian Verheughe wanted to communicate his vision. This included topics such as strategic domain-driven-design, data-highways, and how to use event-driven architecture to further decouple our services. This theme continued, with the first external presenter. Jan Ove Skogheim from Particular Software talked about his experiences from Rikstoto, and how they had broken up a monolith into multiple small services. He also talked about the composite-UI pattern. After lunch we continued with a presentation by Karsten Mevassvik from finn.no, of the most important properties for a finn.no microservice. These include: Is RESTful Owns its own data-store Team ownership Consumer Driven The first day of the summit was concluded with a presentation of the CQRS architectural pattern. This presentation was held by Idar Borlaug and Andreas Berre from WebStep. They showed all the central concepts in CQRS, such as commands, event-stores, aggregates, sagas using very good examples to illustrate their concepts. The second day of the summit started off with some hardcore programming. The frameworks of choice was node.js and RxJava. Christopher Kolstad started with an example of how a microservice could be implemented using Reactive Streams and RxJava. After that Phillip Johnsen presented a case using node.js in a real time context