Real Time JavaScript Web Apps with WebSockets, SSE, and WebTransport

UpdatedMarch 13, 2025

Senior Software Engineer specialising in cloud architecture, distributed systems, and modern .NET development, with over two decades of experience designing and delivering enterprise platforms in financial, insurance, and high-scale commercial environments. My focus is on building systems that are reliable, scalable, and maintainable over the long term. I’ve led modernisation initiatives moving legacy platforms to cloud-native Azure architectures, designed high-throughput streaming solutions to eliminate performance bottlenecks, and implemented secure microservices environments using container-based deployment models and event-driven integration patterns. From an architecture perspective, I have strong practical experience applying approaches such as Vertical Slice Architecture, Domain-Driven Design, Clean Architecture, and Hexagonal Architecture. I’m particularly interested in modular system design that balances delivery speed with long-term sustainability, and I enjoy solving complex problems involving distributed workflows, performance optimisation, and system reliability. I enjoy mentoring engineers, contributing to architectural decisions, and helping teams simplify complex systems into clear, maintainable designs. I’m always open to connecting with other engineers, architects, and technology leaders working on modern cloud and distributed system challenges.

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Preventing Broken Object Level Authorisation in ASP.NET Core APIs

An authenticated user calls your API with a valid access token. The token contains the right role and the endpoint requires authorisation. Everything appears secure. The user then changes /claims/8d61

Jul 18, 202610 min read126

Preventing Broken Object Level Authorisation in ASP.NET Core APIs

Cutting AI Prompt Tokens by Turning Text into Images with .NET

Sending text to an AI model as an image sounds like it should cost more. The application has to render the text, encode a PNG and send a much larger payload over the network. Yet for the right kind of

Jul 18, 202612 min read105

Cutting AI Prompt Tokens by Turning Text into Images with .NET

Building SSRF-Resistant HTTP Clients in .NET

Applications increasingly accept URLs from outside their own code. A webhook tester calls an endpoint supplied by a customer. An image service downloads a remote avatar. A document pipeline retrieves

Jul 17, 202612 min read132

Building SSRF-Resistant HTTP Clients in .NET

What If Your Pull Request Had a Blast Radius Score?

Some pull requests look harmless until they reach production. Then someone notices the change touched authentication, a shared response contract, an EF Core migration, and one production config value

Jul 7, 202618 min read119

What If Your Pull Request Had a Blast Radius Score?

Building a tiny IRC client in C#

IRC is old, plain, and surprisingly useful as a teaching tool. You open a TCP connection. You send text commands. The server sends text lines back. The connection stays open. If the server sends PING,

Jun 24, 202612 min read145

FullStack City

89 posts

Software development & engineering blog

Building real time web applications requires efficient communication between the client and server. Whether updating a live dashboard, enabling instant messaging, or synchronising data across multiple users, the right technology makes a significant difference. Traditional request response models introduce unnecessary delays, which can be avoided using persistent connections that keep data flowing without repeated polling.

WebSockets provide full duplex communication, allowing data to move freely between client and server without waiting for a request. Once a connection is established, messages can be sent in either direction instantly. This makes WebSockets an ideal choice for chat applications, multiplayer gaming, and collaborative tools. A typical implementation involves setting up a WebSocket server and handling messages asynchronously.

const ws = new WebSocket('wss://example.com/socket');
ws.onopen = () => {
    ws.send('Hello server!');
};
ws.onmessage = (event) => {
    console.log('Message from server:', event.data);
};

For scenarios where a one way data stream is sufficient, Server Sent Events (SSE) offer a lightweight alternative. The client establishes a persistent connection and listens for updates, but unlike WebSockets, communication flows in one direction. This is particularly useful for stock market tickers, live news feeds, and notifications. Since SSE operates over standard HTTP, it benefits from reconnection handling and works well with load balancers.

const eventSource = new EventSource('/events');
eventSource.onmessage = (event) => {
    console.log('New event:', event.data);
};

A newer option, WebTransport, is gaining traction for scenarios demanding low latency, high performance communication. Built on top of HTTP/3, it offers a more efficient way to handle unreliable or ordered data delivery compared to WebSockets. This is particularly relevant for streaming video, online gaming, and IoT applications where reducing overhead is a priority. While WebTransport is still evolving, it provides advantages in bandwidth efficiency and security, making it a strong contender for modern real-time applications.

Choosing the right technology depends on the specific needs of the application. WebSockets excel in bidirectional interactions, SSE simplifies server-to-client updates, and WebTransport unlocks new possibilities for latency sensitive communication. As real-time functionality becomes a standard expectation in web applications, leveraging the right tool ensures a good user experience with minimal performance trade offs.

Command Palette

Comments

More from this blog