Personal blog of Yzmir Ramirez

In Episode #134 we talk about Highly Available websites with Drupal.

Show Notes

• Defining what we mean by high availability and defining availability with a customer.
• High availability scenarios – “Today Show Affect”
• Traffic patterns and history, understanding your customers needs and schedules
• How to determine if a customer needs high availability
• Implementing high availability – single points of failure, components of HA and overview of strategies
• How to learn more about HA website implementations
  • Checkout Digital Ocean and Amazon AWS for learning and playing
  • HA is not point and click… heavy DEVOPS
• HA Drupal providers
  • Acquia and Pantheon
• Disaster recovery (a future show is needed for this)

Module of the Week

https://www.drupal.org/project/christmas_lights

A splendid module with Christmas lights decoration that creates long lasting atmosphere of X-mas for you and the users of your website.

Bonus Content

Mark Meier from Load Impact joins Nic and Stephen to demonstrate Load Testing with his product Load Impact. Mark has provided a very special offer to receive double the Virtual Users with a subscription. Sign up fo Bonus content at www.talkingdrupal.com/newsletter

Hosts

Stephen Cross – www.ParallaxInfoTech.com @stephencross

John Picozzi – www.oomphinc.com @johnpicozzi

Nic Laflin – www.nLightened.net @nicxvan

In Episode #134 we talk about Highly Available websites with Drupal.

Show Notes

• Defining what we mean by high availability and defining availability with a customer.
• High availability scenarios – “Today Show Affect”
• Traffic patterns and history, understanding your customers needs and schedules
• How to determine if a customer needs high availability
• Implementing high availability – single points of failure, components of HA and overview of strategies
• How to learn more about HA website implementations
  • Checkout Digital Ocean and Amazon AWS for learning and playing
  • HA is not point and click… heavy DEVOPS
• HA Drupal providers
  • Acquia and Pantheon
• Disaster recovery (a future show is needed for this)

Module of the Week

https://www.drupal.org/project/christmas_lights

A splendid module with Christmas lights decoration that creates long lasting atmosphere of X-mas for you and the users of your website.

Bonus Content

Mark Meier from Load Impact joins Nic and Stephen to demonstrate Load Testing with his product Load Impact. Mark has provided a very special offer to receive double the Virtual Users with a subscription. Sign up fo Bonus content at www.talkingdrupal.com/newsletter

Hosts

Stephen Cross – www.ParallaxInfoTech.com @stephencross

John Picozzi – www.oomphinc.com @johnpicozzi

Nic Laflin – www.nLightened.net @nicxvan

 Automile, a fleet logistics and management startup, has closed a $7.5 million Series A round led by SaaStr with participation from Salesforce Ventures, Niklas Zennstrom, Dawn Capital and Point Nine Capital. Automile provides customers with a box to install in under the vehicle’s dashboard to track mileage, trips and provide route tracking. Automile ships its tracking device… Read More

 Salesforce has always liked to think of itself as an industry irritant, the company that was bucking the status quo and making the established players feel uncomfortable. But this year as the cloud mainstreamed and Salesforce took off on a $10 billion run rate, you couldn’t help but feel that after 17 years in business, that Salesforce’s time had finally come. The company went on… Read More

Percona is pleased to announce the release of Percona Server for MongoDB 3.4.0-1.0beta on December 23, 2016. Download the latest version from the Percona web site or the Percona Software Repositories.

NOTE: Beta packages are available from testing repository.

Percona Server for MongoDB is an enhanced, open source, fully compatible, highly scalable, zero-maintenance downtime database supporting the MongoDB v3.4 protocol and drivers. It extends MongoDB with Percona Memory Engine and MongoRocks storage engine, as well as adding features like external authentication, audit logging, and profiling rate limiting. Percona Server for MongoDB requires no changes to MongoDB applications or code.

This beta release is based on MongoDB 3.4.0 and includes the following additional changes:

• Red Hat Enterprise Linux 5 and derivatives (including CentOS 5) are no longer supported.
• MongoRocks is now based on RocksDB 4.11.
• PerconaFT and TokuBackup were removed.
  As alternatives, we recommend using MongoRocks for write-heavy workloads and Hot Backup for physical data backups on a running server.

Percona Server for MongoDB 3.4.0-1.0beta release notes are available in the official documentation.

 You could argue that 2016 was the breakout year for Amazon’s cloud computing service, AWS — and Wall Street knows that an even bigger wave is coming next year.
Amazon’s retail business continues to grow, and chug along, and gobble up share from offline commerce and other companies desperately trying to up their e-commerce game. And that’s all fine and good &#8212… Read More

 The internet has changed a lot over the last two decades, but many companies are still using legacy technologies to extract, transform and load their data into warehouses. One new entrant, Xplenty, is hoping that its fresh approach, prioritizing cloud services, will provide a solid foothold in the massive market for data integration tools. Having grown to serve over 100 customers, Xplenty… Read More

 Debugging startup Backtrace I/O was launched to solve a real problem that its founders faced when they were engineers at adtech company AppNexus — at least according to Backtrace CEO and co-founder Abel Mathew. Mathew told me Backtrace aims to “solve the process of debugging,” something that most companies tackle by “cobbling together very old, outdated solutions”… Read More

Take Percona’s blog poll on what programming languages you’re using for backend development.

While customers and users focus and interact with applications and websites, these are really just the tip of the iceberg for the whole end-to-end system that allows applications to run. The backend is what makes a website or application work. The backend has three parts to it: server, application, and database. A backend operation can be a web application communicating with the server to make a change in a database stored on a server. Technologies like PHP, Ruby, Python, and others are the ones backend programmers use to make this communication work smoothly, allowing the customer to purchase his or her ticket with ease.

Backend programmers might not get a lot of credit, but they are the ones that design, maintain and repair the machinery that powers a system.

Please take a few seconds and answer the following poll on backend programming languages. Which are you using? Help the community learn what languages help solve critical database issues. Please select from one to six languages as they apply to your environment.

If you’re using other languages, or have specific issues, feel free to comment below. We’ll post a follow-up blog with the results!

This blog shows the results from Percona’s poll on what database technologies our readers use in their environment.

We design different databases for different scenarios. Using one database technology for every situation doesn’t make sense, and can lead to non-optimal solutions for common issues. Big data and IoT applications, high availability, secure backups, security, cloud vs. on-premises deployment: each have a set of requirements that might need a special technology. Relational, document-based, key-value, graphical, column family – there are many options for many problems. More and more, database environments combine more than one solution to address the various needs of an enterprise or application (known as polyglot persistence).

The following are the results of our poll on database technologies:

Note: There is a poll embedded within this post, please visit the site to participate in this post’s poll.

We’ve concluded our database technology poll that looks at the technologies our readers are running in 2016. Thank you to the more than 1500 people who responded! Let’s look at what the poll results tell us, and how they compare to the similar poll we did in 2013.

Since the wording of the two poll questions is slightly different, the results won’t be directly comparable.  

First, let’s set the record straight: this poll does not try to be an unbiased, open source database technology poll. We understand our audience likely has many more MySQL and MongoDB users than other technologies. So we should look at the poll results as “how MySQL and MongoDB users look at open source database technology.”

It’s interesting to examine which technologies we chose to include in our 2016 poll, compared to the 2013 poll. The most drastic change can be seen in the full-text search technologies. This time, we decided not to include Lucene and Sphinx this time. ElasticSearch, which wasn’t included back in 2013, is now the leading full-text search technology. This corresponds to what we see among our customers.

The change between Redis versus Memcached is also interesting. Back in 2013, Memcached was the clear supporting technology winner. In 2016, Redis is well ahead.

We didn’t ask about PostgreSQL back in 2013 (few people probably ran PostgreSQL alongside MySQL then). Today our poll demonstrates its very strong showing.

We are also excited to see MongoDB’s strong ranking in the poll, which we interpret both as a result of the huge popularity of this technology and as recognition of our success as MongoDB support and services provider. We’ve been in the MongoDB solutions business for less than two years, and already seem to have a significant audience among MongoDB users.

In looking at other technologies mentioned, it is interesting to see that Couchbase and Riak were mentioned by fewer people than in 2013, while Cassandra came in about the same. I don’t necessarily see it as diminishing popularity for these technologies, but as potentially separate communities forming that don’t extensively cross-pollinate.

Kafka also deserves special recognition: with the initial release in January 2011, it gets a mention back in our 2013 poll. Our current poll shows it at 7%. This is a much larger number than might be expected, as Kafka is typically used in complicated, large-scale applications.

Thank you for participating!