Learn about the latest trends in Angular and frontend web technologies in an inspiring, open meet and connect with our speakers and other like-minded, passionate developers.
Meet & Chat
Mamak Chat: Office Hours
Mamak is the Malaysian version of cafe, the place where conversation happens. There will be Mamak Chat after each session. You can discuss topics of your interest further with other participants and also the speakers! Good ideas come from conversation, so let's have a chat or... join and listen what's others have in mind.
Building your first Fullstack Serverless App with Angular
In this workshop we will be introducing AWS Amplify a modern toolchain, libraries and UI componen...
On the BlueWeb project, which is a project to completely rewrite the B2C web applications of Air France and KLM, we have been using Angular since the early days. We started our project on Angular 2.0.0-rc.2. We are using this in combination with GraphQL on the server side, quite an interesting setup. Since AirFrance-KLM is one of the biggest airlines groups in the world, it is quite an important and big platform for the company.
There’s multiple ways to split a big Angular project, we’ve tried multiple different solutions within Air France KLM and over the years the project has changed and evolved in the set-up.
- Single App (single repo)
- Micro Front End Architecture (multi repo)
With our story we want to show you what we have learned and show the multiple options there are and what to consider when building a large scale Angular app and not to make the same mistakes as we have made.
In a talk we gave at GraphQL Summit San Francisco in 2017 you can see where we started (https://www.youtube.com/watch?v=T2njjXHdKqw). Also we recently shared a blogpost on medium on how we deal with upgrades in Angular. This blogpost was shared by all the big Angular contributers and also mentioned by Brad Green during NgAtlanta. You can read the post here: https://medium.com/airfrance-klm/how-we-upgraded-a-website-with-half-a-billion-annual-users-to-angular-7-in-less-then-a-day-71de33a1108e
As you can see we can’t stretch enough on how important it is to stay with the latest Angular release. And also why it doesn’t have to be scary for big companies to work with these new technologies and how it enables you to roll out a new version of your application on a daily basis as long as your mindset and set-up is correct. We can talk about why companies should be releasing smaller chunks but more regularly and how to get there:
- Branching strategies
- Automated Testing
- Mobile Device Testing