Lasagnoli

A recipe for success...

  • Autonomous teams
  • DRY code
  • Fullstack mindset
  • Consistent tooling
  • Developer mobility
  • Modular CI/CD
  • High rate of change

...which ever way you want to slice it!

Pasta paradigm by decade
Dig in...

How did we get here?

The pasta metaphor was for software engineering was first introduced in 1994(!) by Raymond J. Ruby

AWE.SOME

The key ingredients

A lasagnoli architecture combines the best of a layered services (lasagna)
with the vertical domain oriented approach of microservices (ravioli).

Monorepo

Monorepo

The key technological enabler of the lasagnoli approach.

Shared libraries

Shared libraries

"One tool to solve one problem" curtails proliferation of technologies and allows for a high degree of reuse.

A lattice team structure

A lattice team structure

Product teams organized around a domain (vertical) with guilds organized around technology (horizontal). This allows for a high degree of autonomy and alignment.

Modular and universal CI/CD

Modular and universal CI/CD

Keeps building artifacts fast, manageable and understandable. MPyL is a tool that helps with this.

...to a tasty lasagnoli!

Registration

Maecenas pulvinar ultricies dolor, vitae sagittis nunc aliquam non. Cras vitae eros mi.

© AWE.SOME