Skip to main content

Ordina Stand out from the crowd on May 26th

On May 26th, Ordina Belgium(the company I work for) is organizing a free technology event. Ordina’s technology specialists will give 21 30 minutes sessions, spread over 5 tracks. The event is free for everyone to join, registration is required. You can register here: www.ordina.be/differentiate.

ThumbPrint

We will have the following sessions for you to attend:

Agenda: Stand out from the crowd with Microsoft technology on May 26, 6 pm
30-minute sessions – the choice is yours

  • .Net
    Visual Studio LightSwitch
    Building a Windows Phone 7 application: lessons learned
    C#5 Async
  • SharePoint
    Automated scripted deployment of SharePoint
    SharePoint 2010: architectural overview
    Developing against SharePoint 2010 lists
  • SQL
    Where .Net meets SQL Server: SQL CLR
    Extending to multilingual reporting
    Using geo data within Report Builder 3.0
  • Application Lifecycle Management
    Automate your deployment cycle with TFS Build 2010 and Workflow 4
    Delivering quality software with TFS 2010
    Team Explorer Everywhere: TFS and Java, better together
  • Azure
    Reporting services in the cloud
    Moving a legal application in the cloud
    Windows Phone7 and the cloud
  • Infrastructure
    Unified Communications: Lync
    Unified Communications: Office 365
    Hyper-V
  • Enterprise Portfolio Management
    Demand management using workflow in Project Server 2010
    Bridging the project and work management gap

I will be talking about Windows Phone 7, Team Foundation Server 2010 and I also present our very own keynote together with Gill Cleeren.

Interested? Join us!

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         ...

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) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...