Rearchitecting a smelly enterprise pattern
Writing this post is intended to act as a spur for myself to, as much as an exposition on a sane decomposition and decoupling of a small monolithic.
The background is a pattern which had emerged in two entirely separate enterprise systems at two very large UK-based media companies (you could take a wild guess, just looking at our landing page). Both systems were intended to firewall a high-volume client-facing service from a large, metadata database.
Future posts will (unless you’re watching on “Dave”) detail a skeleton implementation and microservice-y reimplementation, which should prove to decouple the systems more effective and provide a more obvious roadmap.
That doesn’t sound too zingy…. I ought to start with some graphics.
Publishing a markdown CV with Github, Travis, Docker and Pandoc
About 6 months ago I started trying to work with simplified CV using Markdown.
Now I’ve got a CV which is source-controlled, and is published in multiple formats (HTML, PDF, Word) on commit.
I had to use this feature in anger today having spotted the word ‘technoolgy’ in a Word-rendered version.
What I haven’t done (yet) is have it /pushed/ to any potential readers.
Here we go again
Despite being a small company, I’m happy to take on multiple work streams. Several years of various agile environments has given me a real insight into how to manage multiple work streams.
I’m still primarily an engineer.
So apart from my first work stream developing for Sky’s new OTT video backend, I need to develop a company site and brand.
Tracy chose the name ‘Belle Software’ after our Labradoodle puppy and we agreed it fitted the bill.
####Choosing a website technology
I need to advertise my wares (ok… services) but there’s a point. However I also want to consolidate and practice what I have learned about site manangement.
- I want to steer clear of dynamic or CMS-driven - they’re hard work and fragile. Having a database is millstone, even if it’s wrapping in a CMS.
- Version Control (VCS) is essential.
- A client framework is essential to making the site usable across platforms. I cut my teeth on Twitter Bootstrap recently so that’s what I’d like to stick with for now.
- The logic choice for many devs in my position is Jekyll, despite many carps about its limitations. I can also make use of github.io linked with a custom domain.
- Other people are better at site design that me - I’m good at reusing and repurposing.
I found a gem in a Jekyll port of the Solid theme.
Subscribe
Subscribe to this blog via RSS.
Categories
Github 1
Travis 1
Docker 1
Pandoc 1
... 2
Recent Posts
-
Posted on 16 Dec 2015
-
Publishing a markdown CV with Github, Travis, Docker and Pandoc
Posted on 16 Sep 2015 -
Posted on 01 Sep 2015
Popular Tags
Github (1) Travis (1) Docker (1) Pandoc (1) ... (2) Enterprise (1) Dropwizard (1)