It’s been a while since I’ve written, funny that I’m about to write about something else that I haven’t done in a long time. I will be attending the PASS Data Community Summit next week (Nov 14-17th).
I will be delivering a presentation on Thursday(11-16) at 4:45-6:00 pm in Room 401. This will be the first time I’ve ever presented at the PASS Summit. Even though I used to attend this event every year I actually never wore a speaker badge. It was one of those things I always wanted to earn in my career. Somewhat funny how you leave something for many years and when you come back you can get the one thing you wanted.
For a quick little history. From about 2004 until 2016 I attended, volunteered, helped organize, and documented in very many pictures the Community we commonly call #SQLFamily. This was truly some of the best times in my life with these wonderful individuals that I really see as family. I’m very eager to be part of that community once again and catch up with old friends.
I’m also very excited that I’ll get some much-needed Photowalk time in Washington, this was a tradition we started to get out and see the area around us and take pictures. I’m planning a hike and waterfall expedition on Sunday that will not be anywhere near the city!
I’ve really looked forward to this event for the whole year! I have one little minor event to take care of on Friday (Big Mountain Data and Dev Conference, you can still get tickets!), then I’ll be packing my bags and heading out!
Can’t wait to see the #sqlFamily again! In case you want to take a little stroll down memory lane for any of my PASS friends. Enjoy.
I always kinda see a fight in my mind when someone mentions Relational/Non-Relational. I took this picture long ago and some good friends are posing for me.
This post is in relation to the #PGSQLPhriday blogging series. The original post for this discussion is located here. Thank you Ryan Lambert for such a great topic and for hosting this month!
Ryan posted a challenge on how are you using Postgres. I felt like for this post instead of focusing on one question. I would simply answer all of them! I really liked all the questions so I’m just going to answer them!
What non-relational data do you store in Postgres and how do you use it?
In the current company/PG servers, I work with and deal with. We have a great number of JsonB columns that house Non-relational data. I am newer to this company so really didn’t have much of a say in the design of this particular aspect. Currently, it’s primarily used as a logging/settings store in those JSONB columns. It was a pattern that was created with good intent but misused. Turning into the Data Junk Drawer. Unfortunately, the data is needed in many cases and so you have procedures/functions out there trying to query the data out of these fields and use it in various cases. This is not an ideal use for it.
One good example of non-relational data used well. I did some contract work for a document scanning company that would use OCR to read most of the data/metadata about the documents and put them into table structures and then store a link to the actual document in a file store. This link was added to the row so the application could retrieve the document but it wouldn’t be actually stored in the DB. The performance issues they called me for were still related to the data they were trying to scan but it was mostly bad indexing. Once we corrected the indexes everything worked much better and they had a good system that would scale reasonably well.
Have you attempted non-relational uses of Postgres that did not work well? What was the problem?
Yes, Besides the current system, I mentioned above for the “Junk Drawer”. I also ran into another company that did store logos/graphics/images for the website in the DB. The retrieval from the DB wasn’t really horrible since they were pulling exactly a row/column from the DB, the real issue came along with caching. Websites can’t take 2 minutes to pull up images and documents and they depend on the cache to make them run fast. The web servers of the time couldn’t cache the documents since they were DB calls and not static documents. This means that each website load had to re-pull the data. Once this system started scaling and getting lots of requests the web servers couldn’t keep up re-loading the images over and over. In the end, they had to move this out of the DB and into the Webserver cache where it belongs. I strongly urge all of my customers to never store images/graphics in the DB at all if they can avoid it.
What are the biggest challenges with your data, whatever its structure?
Right now the biggest challenge for the current project/company I work for is just related to DB sprawl. We have 10+ years of the DB being designed with a monolithic application that added new tables all into the same DB. Only a few of the functions/design of the application was broken apart into separate pieces, separate schemas, or really separated at all. This is not uncommon in the industry since many companies that have been building software for 10-15 years started out with monolithic applications and rarely do we go back and focus on the technical debt side of things. Moving systems like this to a Service Oriented Architecture or even just breaking it up into different pieces takes time and a lot of cultural change for a company. It’s always a long-term project and usually, in a larger company it will take years to complete. It’s a fun challenge to have and you can find small wins by breaking off smaller pieces and starting on new products/new features in a new system.
How do you define non-relational data?
I like to define data based on how it’s used. I tend to see a lot of various data with companies so I tend to keep an open mind and just base my definitions on how the data is used. An example of this is Search, We all know PG and many RDBMSs can have indexes and search very quickly through millions of rows of data. I’ve found in past experiences that moving heavy search functions off to something like Elasticsearch has been a great way to speed up search even more. RDBMSs are really not great at doing textual style searches vs something like an Elasticsearch engine. It’s an excellent example of using the right tool for how the data is being used.
I really enjoyed this #PGSQLPhriday, I hope more in the community will join in the fun and join us in a future #PGSQLPhriday. Thank you Ryan Lambert for the great topic!
My first attempt at a little AI art, Made with Open AI Dall E 2.
This was a write-up I did for my company to explain what Speaker Idol was and how it could be used to get more speakers for our internal training at the company. Since I was writing it up for internal use, I would also go ahead and make a blog post.
Speaker Idol is a concept/idea that allows a group to gather more speakers for future events. If you are at a meetup and you are trying to fill your speaking roster for the year, this gives you a method to do that. It also helps to grow your speakers and help new speakers get started. The goals of Speaker Idol are simple.
Give a new speaker the chance to speak in a safe, supportive environment, and with minimum preparation time. This removes the barrier to entry for new speakers.
Grow the speaker pool you have available to you as an organizer of events. Whether that’s a user group/meetup/conference.
Teach new speakers with constructive feedback about how to improve the session.
This is not a new idea, I do not take ownership of coming up with this idea. I used this successfully in a few user groups I’ve run and have continued to use it. It is another tool that community individuals can use to grow the community around them.
What is a Speaker Idol presentation?
Put simply it’s a full presentation where you only present one portion of it.
New speakers tend to have a big idea! Perhaps something like “RDBMS Internals”. This is a little large for a first-time speaker to be taking on. It could literally be hundreds of presentations to make that concept work. But if they can think of one specific idea like, “Pros and Cons to clustered indexes”. This is something that could be one part of a presentation called “Indexes in an RDBMS”, in that larger presentation you might be talking about many different types of indexes and you intend 1-2 slides on the “Pros and Cons of clustered indexes”. Perhaps you had a demo to show the advantages and what’s good and bad about them.
This is how you would break down a speaker Idol presentation. For a brand new speaker, we can coach them that they just need 1 idea, 1 demo, and a few slides to talk about the presentation. Once they have gotten over this hurdle they can then present the full presentation. They also have the building blocks and time to build the rest of the presentation.
Grow the Speaker Pool
Once someone presents a short presentation at Speaker Idol the goal is to have them come back to the group and do the full presentation. Consider the short presentation as a preview of the real thing. This helps to grow speakers, it also gives organizers more presentations to fill out the year. It is your responsibility to keep fostering that new speaker and encouraging them to come back and do the full presentation. Most of the time when a speaker gets over the initial hump of presenting they want to keep doing it. This is not true in all cases though so please don’t push people that they are required to do the full presentation. Presenting might not be for them and most importantly you still want to keep them as a member of the community.
Constructive Feedback
The best way to improve as a speaker is good feedback from your audience. Speaker Idol is designed to help with this for speakers. The beginning of every Speaker Idol session starts with a quick 5 minutes on how to give “constructive speaker feedback”. The key items are listed below, you can change these as you need.
Please be detailed in your feedback and tell me how we can improve. Good examples:
“Speaker needs to talk louder”
“Speaker needs to engage the audience”
“Speaker should be better prepared and have tested demo to make sure it worked properly”
Bad Examples:
“Speaker sucks” (Tell what they did wrong)
“Boring session” (Tell why it was boring)
“Worst session of the day” (Tell why and what went wrong)
Tell the speaker what you did/did not like about the session. “Good examples”
Loved the jokes/comedy, I really wished you would have reviewed this query in more detail.
You had great attention to the audience but kept forgetting to repeat the question, Please do so in the future.
I was really hoping to see X information in this presentation since that’s what I got from the Abstract.
We use a simple google form that allows for audience members to leave feedback. I know that in most presentations you don’t get a lot of this. That’s why Idol has to focus on it and mention that people should go fill out the form while the next presenter is getting ready. If you are in person’s hand out the forms and say a drawing will be based on the forms handed in. Even if it’s online create a drawing for the audience based on the feedback. This greatly improves the chance of getting feedback. It’s critical that whoever is running speaker idol reminds everyone to give feedback.
Each presentation should be longer than 5 minutes but less than 15 minutes.Q&A is included in the time. TIP – focus on one topic and one demo, you are trying to get one key point across of a bigger idea.
You still will need an Abstract and Bio for the presentation. TIP – This is a common practice in presentations and you should get used to writing them.
That’s it, Pretty simple, right? Here are some more tips.
If you have 1-hour meetings schedule 3 presentations. This gives your audience a good mix of presentations and if you have a big list of participants you can get through. It should give you enough buffer time for feedback and talking as well.
Plan a speaker gift! Originally we had this as a competition and crowned a 1st, 2nd, and 3rd place winner. You are welcome to do that. I found in later years I really just wanted to grow speakers and grow the community so I moved this to a speaker gift for those that took part. This is entirely up to you.
Plan an audience feedback drawing. As mentioned above feedback goes better if you have a drawing for it. Plan to get a couple of gift cards or something that you can draw from the feedback.
Give the feedback quickly to the speakers, If you do an online form and you have to do any parsing/work to get the data out of the form make sure you do it quickly after the presentation. The more immediate you can make the feedback to the presenter the better.
DO NOT open up the session for public feedback and discussion. If you are a small internal team in a company this is OK, if you are a meetup/user group/public meeting with many different people make sure this feedback is done through a form method.
Do an “Introduction to presenting/Speaking 101” presentation for the new speakers before the event. Typically about 2-3 weeks before so they can adjust the presentation if needed. I have videos I’ve done on this in the past you can use or you can create your own. <link to past video I did for this. Apologies for the not great audio>
I’ve found in years past this is a great way to kick off your year as a user group leader. It gets people excited and gets a lot of future presenters for you to work with. Hopefully, you can use this concept to grow your community!
Sql Insane Asylum (A Blog by Pat Wright) 