Norfolk Tech Journal Issue 03 Out Now!

It’s hardly surprising that pretty much everyone has heard of Silicon Valley. The term has been about for over 40 years and has become synonymous with hi-tech companies. Silicon Roundabout, despite the media coverage of late, is decidedly less ubiquitous, especially outside of the UK. Silicon Broads? You’re going to draw a blank from many there.

This lack of recognition is a problem for Norwich and Norfolk, one that a number of technical groups in the area are striving to address. The term Silicon Broads is just jumping on the “Silicon X” bandwagon and is never going to get the same acceptance as the original term, but I also think it’s missing the point. We don’t have chip fabrication plants in Norfolk, we have technical people, and a surprisingly large number of them.

The great thing about people is that they know other people. It’s these networks that companies like Facebook and Twitter have cashed in on. Get enough people together and the potential reach through their networks is astounding. This is precisely what the recent SyncNorwich Tech Crunch event was about: get a large enough group of technical people together to make people sit up and take notice.

Of course getting 300 people together for an event is easier said than done. Having Mike Butcher, Editor-at-large for Tech Crunch, as your headline speaker certainly helps though and John Fagan pulled off a huge coup for the region by getting him to come to Norwich. By using Mike as the glue, SyncNorwich were able to put together the largest tech event the city had ever seen, showcasing local startups and attracting everyone from students to CEOs.

The sheer volume of coverage from social media, blogs and local press shows the event tapped into something. Norfolk has announced its presence on the tech map, and it’s not just here to stay, it’s here to be an increasingly important player in Digital Britain.

The Norfolk Tech Journal is out now and can be downloaded for free here.

Words: Dom Davis

Comments

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...

Paul Grenyer

Search This Blog