You’ll hear this talk at Elm Europe in June 2017. Massive thanks to @chrisui, @stealthpig, @zsoobhan, @spryle, @dumbNickname and everyone else who helped shape this proposal. You guys are awesome!
Choosing the right technologies when starting a project is super important. It’s almost impossible to change the stack later on. Betting on Elm is therefore a bit risky. Right?
Not anymore! Now we can use frontend microservices to pick the right tool for every job!
Traditionally, single page apps are monoliths. Here’s a React app, that’s an Angular app and this one is in Vue.js. This way, early stack choices turn into a strong tie-in as the project grows. It’s pretty tricky to introduce Elm to a mature project running on a different technology.
In this talk, we’ll see how web components change the game. Finally, we can use the right tool for every job! We can introduce Elm bit by bit to any JavaScript app – or neatly embed JavaScript UI nuggets in an Elm app.
We’ll learn from the ups and downs of regular microservices, catch a glimpse of the culture that this approach has brought about at Lystable and leave with a strong toolset to make things happen.
speaker
Tomek Wiszniewski
Tomek created elm-live – a tool widely used and loved by the Elm community. As an engineer at Lystable, he crafts delightful user interfaces and helps shape an engineering culture which allows everyone to unleash their superpowers.
With a degree in Architecture (yeah, building houses), he’s been using Elm for a number of exciting University projects – and a mind-blowing app for makers coming to the market soon.
Hey @dumbNickname, thanks so much for the thoughtful comments! The overview from compoxture is super helpful.
People have been doing frontend microservices that way for a while now – putting content from different applications together into a single, SEO-friendly HTML stream. Also, I hear great stuff about Varnish and ESI! My talk was mostly about developing single-page apps though, and in that case there’s little or no dynamic content that you want to deliver from the server.
But if you have a mixed “content + app” site – or want to boost performance through a server-side prerender – you can actually use the server-side caching/streaming tech you mentioned and frontend microservices alongside. 🎉 You can render content inside a web component and have it replaced when JS kicks in. That’s how the skeleton worked in the example app I showed. You can even pick up the prerendered DOM and reuse it in JS.
I’ve rephrased the intro to be 100% accurate. And I’ll definitely keep your other thoughts in mind. Thanks again! 😀