Skip to main content

Mini-SPA’s(Single Page Apps)

After building multiple both small and large Single Page Applications I’ve landed on an approach where I typically split out my single Single Page App into multiple smaller SPA’s. Similar to using microservices on the backend this approach offers a lot of benefits.

First of all the initial footprint of your application is a lot smaller. Second working with multiple people on a SPA becomes easier, less change that something is broken after pulling the latest sources from your source control system. You can also avoid some of the issues regarding session expiration, javascript bugs that make your app freeze, memory leaks, etc… that you otherwise need to handle yourself.

However each time I start a new project and I try to explain this approach to someone I get strange looks and people doesn’t understand why you shouldn’t build your SPA as one big monolith?

Last week I stumbled over a blog post by Maurice De Beijer where he explains a similar approach. Now I feel confirmed in my opinion Smile

Are there other people out there who split out their SPA?

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more