Readers List of 2020
In 2020 I've written a couple of interesting articles. In this post I want to list the top 15 articles of this year.
If you are interested in making microfrontends work, you'll also need to have them communicating with each other at some point. I've written a post that covers exactly this. Read more on Bits and Pieces.
Azure Pipelines has been enhanced a lot in the last year. One of the reasons was the introduction, broad rollout, and enhancements to their YAML capabilities. I've written a post going into more details. Read more on ContentLab.
Again, microfrontends are important and will fully break through in 2021-2022. One of the reasons is that you can use cross-framework components. This article shows you how to do it efficiently from scratch. Read more on Bits and Pieces.
Another thing that is around the corner is React's concurrent mode. Yes, already out there (experimentally), this can be used today. How, why, and when is discussed in another post I've written. Read more on LogRocket.
With my journey into microfrontends being quite deep I tried to summarize what my understanding of the state of microfrontends is. Read more on Bits and Pieces.
CI/CD pipelines remain to be important. One cool tool is Concourse CI. Using Conjur we can quite nicely manage secrets and keep important information restricted. Read more on Conjur.
For anything related to APIs Postman is a tool that cannot be dropped. It supports collections and unit testing, too. The swiss army knife of API development tools deserved its own article. Read more on OneLogin.
React's ecosystem is huge. One of the reasons is that there exists at least two libraries for any kind of component. Especially for datagrids the landscape is huge. I've written a small guide on this one. Read more on GrapeCity.
Map controls are so crucial for many web apps. There are plenty of SDKs but not many are as feature complete as the package from TomTom. I've written a couple of posts on TomTom. This one discusses custom styling options. Read more on TomTom.
Sometimes people think that microfrontends require a lot of support from libraries and frameworks. The truth is actually far off. While libraries help, many things can be done out of the box. One option is to transport microfrontends with ES modules. Read more on Bits and Pieces.
Kubernetes is super powerful and quite a success story. One of the reasons is that it is so flexible and contains solutions for quite an array of problems. Using arbitrary data sources is one of these solves problems. Read more on New Relic.
I did not want to remain in a potential bubble, so I tried to expand my circle by conducting a small survey about the state of microfrontends. The results have been partially expected, partially surprising. Read more on Bits and Pieces.
One reason that the topic of microfrontends is so complicated is that there are multiple (completely different) ways of implementing them. This post goes into some of the most popular architectures. Read more on Bits and Pieces.
Having automated E2E tests is something that seems necessary to ensure proper scaling in development. Using the headless recorder tool gives us an edge here. Read more on LogRocket.
With all the hype about microfrontends - is the monolith dead? I'd say no and I have my reasons. Always use a monolith if you can! Read more on Bits and Pieces.