System Architecture

Tucows uses name of dot.com bubble era company to launch new service. Remember RealNames? Tucows has brought back the name of the the dot.com bubble darling, but for a very different purpose. RealNames was a system designed to replace or circumvent domain names. Instead of typing a domain name like Money.com in your browser, you […]

The software giant announces it is taking a 20 percent stake in RealNames and will push for new standards to simplify Web navigation.

This document defines a URI scheme, 'go:' to be used with the Common Name Resolution Protocol. Specifically it lays out the syntactic components and how those components are used by URI Resolution to find the available transports for a CNRP service. Care should be taken with several of the URI components because, while they may look like components found in other URI schemes, they often do not act like them. The 'go' scheme has more in common with the location independent 'news' scheme than any other URI scheme.

People often refer to things in the real world by a common name or phrase, e.g., a trade name, company name, or a book title. These names are sometimes easier for people to remember and type than URLs. Furthermore, because of the limited syntax of URLs, companies and individuals are finding that the ones that might be most reasonable for their resources are being used elsewhere and so are unavailable. For the purposes of this document, a 'common name' is a word or a phrase, without imposed syntactic structure, that may be associated with a resource.

Creating a distributed social media system is all well and good, but how do you address problems like deleted tweets? David Eastman explains. #socialmedia #DIY #tutorial

Build shareable development environments with dependencies, databases and webservers in a matter of minutes.

Overview

Vanus provides enterprises and organizations an innovative Platform for Collecting, Storing, Distributing, and Processing Events at Scale.

“RT @davewiner: For people who appreciate file formats, here's a Mastodon RSS feed for someone who uses hashtags. Nice how they turn those t…”

Since the beginning of the Internet, determining the trustworthiness of participants and published information has been a significant point of contention. Many systems have been proposed to solve these underlying concerns, usually pertaining to specific niches and communities, but these pre-existing solutions are nebulous at best. How can we build infrastructure for truly democratic Webs of Trust?

With git running behind the scenes with every operation, Monokle offers a shortcut to the latest in code collaboration, CI/CD, GitOps and more.

Learn how Stardog's Enterprise Knowledge Graph platform is the key to building a data fabric.

A discussion on the synergies between GraphQL and Graph Databases, data architecture and how ontology models provide the special ingredients.

Navigating through the Star Wars universe with knowledge graphs, SPARQL and GraphQL, using Ontotext Platform

With less time spent firefighting and more on innovating, AIOps can empower engineers and developers to drive bigger strategic gains for their organizations. #AIOps #DevOps #ITOps #SRE

When it comes to hardware, there was not a lot of big news coming out of the Amazon Web Services re:Invent 2022 conference this week. And to be specific,

Ecosia uses the ad revenue from your searches to plant trees where they are needed the most. By searching with Ecosia, you’re not only reforesting our planet, but you’re also empowering the communities around our planting projects to build a better future for themselves. Give it a try!

You can see the benefits of good API design practices all across the API ecosystem, but also across all of the web and mobile applications we use each day. If you suffer from the same condition I do, then you see these frustrating signals across the landscape. However, one of the most critical ways in which poor API design affects how we deliver technology is the API design for our API gateway APIs. Like every other API, the design of APIs for API gateways provide a very honest take of what capabilities a gateway offers. Let me show you with two separate examples:

I’ve looked at all the gateways out there today. I’ve been studying API management since 2010. While there are numerous characteristics that define the next generation of API gateways, in my mind the number one thing that will determine the future of API gateways will be their support for API contracts. This means how they adopt OpenAPI, AsyncAPI, JSON Schema, GraphQL, and Protocol Buffers. You see some of what I am talking about int he way that GraphQL and gRPC APIs operate, but it is starker when you look at how gateways support OpenAPI today. More specifically whether they provide only one of the following areas, or support the spectrum.

single file distributable web server