Whereas this was a venture of my own, with limited funding and 20x the volume. This is not to say that if we did have loadsamoney we would have spent it on purchasing top-of-the-line hardware, flashy monitoring systems or DBAs Okay, maybe having a dedicated DBA would have been nice. Over many years of consulting I have developed a view that the root of all evil lies in the unnecessarily complex data processing pipeline. More often than not, these are workarounds for the underlying database issues e.
In ideal scenario, you want to have all data contained within a single database and all data loading operations abstracted into atomic transactions. My goal was not to repeat these mistakes. Instead of maintaining the supporting infrastructure, I have dedicated my efforts to eliminating any bottlenecks by minimizing latency, provisioning the most suitable hardware, and carefully planning the database schema.
What we have is an easy to scale infrastructure with a single database and many data processing agents.
Michael Stone Explains His Scale of Evil
I love the simplicity of it — if something breaks, we can pin point and fix the issue within minutes. However, a lot of mistakes were done along the way — this articles summarizes some of them. I am a co-founder of a company Applaudience. We aggregate cinema data.
- Walking the Line Between Good and Evil: The Common Thread of Heroes and Villains?
- eprom reader programmer for vehicle passive transponder key specification.
- completely free reverse phone number lookup.
Our primary dataset includes movie showtimes, ticket prices and admissions. We combine this data with all sorts of supporting data, including data that we get from YouTube, Twitter and weather reports.
The end result is a comprehensive time-series dataset describing the entire theatrical movie release window. The goal is to predict movie performance far into the future. Every time a person reserves or purchases a ticket from either of these cinemas, we capture a snapshot describing attributes of every seat in the auditorium.
This adds up to 1. We went through several providers:. Google 2. Amazon 3. We got USD k in startup credits from Google. This was the primary deciding factor for choosing their services. This was a known bug that is fixed in newer PostgreSQL versions. The lack of response from the support acknowledging the issue was a big enough red-flag to move on. I am glad we did move on, because it has been 8 months since we have raised the issue, and the version of PostgreSQL has not been updated:.
How to Not Be Evil – Dr. Phil Zimbardo (#) | The Blog of Author Tim Ferriss
As Amazon announced Timestream their own time-series database , it became clear that this requirement will not be addressed in the foreseeable future this issue has been already open for 2 years. Then we moved to Aiven. It had all the extensions that I needed including TimescaleDB , it did not lock us in with a particular server provider meaning we could host our Kubernetes cluster on either of the Aiven.
However, what I have overlooked is that you do not get superuser access. This resulted in numerous issues e. When this happened, support offered to upgrade the instance to one with a larger volume. While this is a fine solution, it caused a longer than necessary outage. Someone with SSH access could have diagnosed and fixed this issue in couple of minutes. And when we started to experience continuous outages due to what later turned out to be a bug in TimescaleDB extension used by Aiven.
Despite me giving shit to Aiven. Tolerating my questions that are already covered in documentation and aiding with troubleshooting issues. All this time I was trying to avoid the unavoidable — managing the database ourselves. Now we are renting our own hardware and maintain the database. Therefore, you must plan for what features you will require in the future. For a simple database that will not grow into billions of records and does not require custom extensions, I would pick either without a second thought the near instant ability to scale the instance, migrate servers to different territories, point-in-time recovery, built-in monitoring tools and managed replication saves a lot of time.
Britain, by contrast, has been far more successful at covering up its slave-owning and slave-trading past. Whereas the cotton plantations of the American south were established on the soil of the continental United States, British slavery took place 3, miles away in the Caribbean. That geographic distance made it possible for slavery to be largely airbrushed out of British history, following the Slavery Abolition Act in Many of us today have a more vivid image of American slavery than we have of life as it was for British-owned slaves on the plantations of the Caribbean.
The word slavery is more likely to conjure up images of Alabama cotton fields and whitewashed plantation houses, of Roots , Gone With The Wind and 12 Years A Slave, than images of Jamaica or Barbados in the 18th century. This is not an accident. The history of British slavery has been buried. The thousands of British families who grew rich on the slave trade, or from the sale of slave-produced sugar, in the 17th and 18th centuries, brushed those uncomfortable chapters of their dynastic stories under the carpet. Thousands of biographies written in celebration of notable 17th and 18th-century Britons have reduced their ownership of human beings to the footnotes, or else expunged such unpleasant details altogether.
Subscribe to the SaaStr Newsletter
The Dictionary of National Biography has been especially culpable in this respect. If it was geography that made this great forgetting possible, what completed the disappearing act was our collective fixation with the one redemptive chapter in the whole story. William Wilberforce and the abolitionist crusade, first against the slave trade and then slavery itself, has become a figleaf behind which the larger, longer and darker history of slavery has been concealed. It is still the case that Wilberforce remains the only household name of a history that begins during the reign of Elizabeth I and ends in the s.
There is no slave trader or slave owner, and certainly no enslaved person, who can compete with Wilberforce when it comes to name recognition. Little surprise then that when, in , we marked the bicentenary of the abolition of the transatlantic slave trade, the only feature film to emerge from the commemoration was Amazing Grace , a Wilberforce biopic. George Orwell once likened Britain to a wealthy family that maintains a guilty silence about the sources of its wealth. Orwell, whose real name was Eric Blair, had seen that conspiracy of silence at close quarters.
His father, Richard W Blair, was a civil servant who oversaw the production of opium on plantations near the Indian-Nepalese border and supervised the export of that lethal crop to China.
- benchmark report 2007 spend employees background;
- The history of British slave ownership has been buried: now its scale can be revealed!
- Having These Personality Traits Might Mean You're Evil.
- death records search for new mexico.
The department for which the elder Blair worked was called, unashamedly, the opium department. However, the Blair family fortune — which had been largely squandered by the time Eric was born — stemmed from their investments in plantations far from India. The Blair name is one of thousands that appear in a collection of documents held at the National Archives in Kew that have the potential to do to Britain what the hackers of WikiLeaks and the researchers of PBS did to Affleck.