VoltDB stored procedures are Java classes. You add some SQL statements, pass them to magic functions and Wingardium Leviosa – a high-performance DB that’s all nice and Java-like. Right? Right?
Not quite. Writing correct, performant VoltDB stored procedures can be a little bit fiddly. I’ve written about this before. Here’s a listicle that tries to catch it all in one convenient checklist.
Capturing these instructions here, just in my case my laptop fries its own graphics drivers (damn you
sudo update-mime-database /usr/share/mime) and I decide it’s easier to reinstall Ubuntu than fix them…
Any modern website worth its salt enforces HTTPS. The first critical step in this is to get a certificate whose root is trusted by modern browsers. Until recently, that meant paying a lot of money, but now it can be done for free with LetsEncrypt and a minima of technical nous. This blog post is how I did it for a Heroku-hosted web app. It’s a step-by-step reference so I can save my future thinking for other things and maybe it’ll be useful for other people too.
To put a VoltDB instance into admin mode you can use the
@Pause stored procedure or the
voltadmin pause CLI command. Likewise, to take a DB out of admin mode, you use
voltadmin resume. But how to check if your DB is paused or not?
Over the last 20 years or so, programming has changed radically. The internet gets the credit and is to blame. The two worlds look as different to the coder as modern Boston would to the New England settler of yore…
Now? It’s all going to change again…
At Socrates Germany I heard a couple of dev’s tell me distributed systems weren’t needed, and many more say that they were too hard and too scary…
So here are some slides from my LSCC talk: a gentle introduction for devs to distributed systems and why we need them, with (almost) no maths or theory required:
And since I can’t be bothered writing any more words, here are images from some of the slides…
// I originally ran into this problem and fixed it with WebStorm, but then found another fix via BrowserSync – see the addendum at bottom for more detail
WebStorm is a great IDE for building web apps, front end and back end, and it works on Linux and all the other major OS’s. But the wonderful help links scattered throughout the product don’t always work right out of the box in Ubuntu 14.04 without some WebStorm setup. Here’s what’s wrong and how to fix it (with thanks to Elena and the fantastic WebStorm community support forum)