Win a copy of The Career Toolkit this week in the Jobs Discussion forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
  • salvin francis
  • Frits Walraven
  • Piet Souris

Micro Frontends in Action: how it started?

Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I love the idea behind your book, I really believe the world needs more a way to work together rather than being isolated.
So I believe the core foundation of having fun programming web apps and not being limited to use any technology is a great principle.
The web itself is amazing as its foundations is the openess and help humanity on his most complicated activity, the communication.

I would love to hear more on how this started and what was your initial steps to achieve what today conforms the content of the book?
Posts: 11
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks. I totally agree that many of the micro frontends paradigms are in line with the core principals that contributed to the success of the open web.

I've been a developer in the e-commerce space for over a decade now. The first companies we worked with had rather small development teams of 5 to 10 people. As the companies grew and their online share increased we had a similar effect in multiple project teams: We reached the limit of a single team size. In 2014 we had the chance to build a new e-commerce platform for a German department store chain [1] with the goal to architect the software in a way that enables multiple end-to-end teams working side-by-side with as little inter-team coupling as possible. We opted for a Self-Contained Systems [2] approach and were able to produce quick and high quality results. We had teams staffed with developers from different companies working on this project. The SCS definition was very helpful, but it focuses on the backend architecture. We had to figure out a lot of user interface integration mechanisms and best practices by ourself. In upcoming projects we had the ability to refine and iterate our approaches and techniques. The prior work of the OTTO Group [3] and publications from Gustaf Nilsson Kotte [4] were very helpful in this phase. These focus primarily on server-generated markup. With the rise of frontend frameworks like React we also felt the need to come up with a good solution for client-rendered applications. The results of our experimentations and research is documented here [5].

Hope this gives you a rough idea on where I'm coming from and how the topic has evolved for me over time. Feel free to ask more questions. I'm happy to go more into detail on this topic.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic