Sharing Top Content from the Angular-sphere.

Micro frontends for the win! – Erhan Gundogan – Medium

  • Team was motivated, goal was clear, technologies and tools were ready to use.
  • So we have started to build our application in October 2015.
  • Backend team started to work on API project in parallel.
  • They were eager to split monolith into micro services.
  • CI with multiple environments, automated deployment, application serves from S3 bucket, having swagger definitions and API gateway usage.

My new company was gathering team of front-end developers to build a better performing web/mobile client to get away from monolith ruby on rails application. We were four front-end developers for…

@ReactDOM: Micro frontends for the win! #react #angularjs #bestpractices #microservices #javascript…

He asked to his colleague. “We have supposed to resolve a monolith problem but we have another one now?”

This story has been started with a monolith ruby on rails application in Autumn 2015.

My new company was gathering team of front-end developers to build a better performing web/mobile client to get away from monolith ruby on rails application.

We were four front-end developers for that mission. There were other things to do but single page application was the main task. There were some ongoing discussions about framework to use. We have been told that our company would like to have hybrid mobile application as well. So in theory our code will be used for both web and mobile client. And eventually it will compiled into native mobile application.

Finally it has been decided to start with AngularJS and Ionic Framework after some research. It was good or bad that’s another story. Decision was logical. Because AngularJS was promising future. Mature MVW framework, testing capabilities, big community, plenty of resources and backed by Google.

Meanwhile there were two other options on the table. Angular2 and React.

We have thought that it would be great if we could upgrade to Angular2 by any chance in the future. So it has been decided to align with Angular2 as much as possible.

Team was motivated, goal was clear, technologies and tools were ready to use. So we have started to build our application in October 2015. It would be financial investment platform for our customers. Backend team started to work on API project in parallel. They were eager to split monolith into micro services. Having micro services and having a web client was very popular and demanding solution on that days, as of today.

So we have started and built our platform upon AngularJS and Ionic framework using github. Some well known libraries and tools are used such as TypeScript, jwt, gulp, bower, karma, mocha, chai, sinon, protractor, phantomjs and so on. CI with multiple environments, automated deployment, application serves from S3 bucket, having swagger definitions and API gateway usage.

Yeah but it is getting way bigger than expected. We had first problem on test suite recently. PhantomJS started to crash when we hit 1500 unit tests. That wasn’t a good signal. We have recovered but it opened our eyes. It is getting bigger and we will have another monolith sooner or later if we go in same way.

Micro frontends for the win! – Erhan Gundogan – Medium

Comments are closed, but trackbacks and pingbacks are open.