Voice of the DBA

Category: Editorial

  • The Career Path

    Which career path would you like?

    Most people seem to wander through their careers, taking any job that comes their way. Others have a tight focus, often with a larger goal of ending up as the owner of a company or perhaps the CIO of one.

    However for the technical person, someone that wants to remain employed for a long time, but doesn’t want to oversee others, there isn’t a clear path. So many DBAs, developers, and other people have no interest in moving into management, but they still would like to progress in some fashion to other jobs.

    This Friday I wanted to ask what that progression might be like if you had no restrictions from HR and could design your own set of jobs:

    What would you like your technical career path to look like?

    I am wondering if you think there ought to be some way to advance to a senior person, maybe with multiple levels after your title. Perhaps some of you would like to move into an architect position or even be seen as some technical fellow after some amount of time.

    Think about the way that a technical career might advance, without going into management, and let us know in which direction you wish you could move.

    Steve Jones

    The Voice of the DBA Podcasts

  • The Woes of Cloud Computing

    Cloud computing: sunshine or rain?

    Many people have been skeptical about the move to cloud computing, especially in the database world. There are valid reasons to worry about security, legal issues, and more. I certainly think that using cloud services requires some planning and careful examination of the impact to your environment, but I also think that many companies will want to make the move, so it pays to learn more about cloud computing and be prepared with realistic, rational concerns from the database perspective.

    Anthony Skipper of ServiceMesh gave a presentation on some of the problems and lessons learned from moving to cloud computing. It was picked up in an Information Week piece that summarizes some of the areas that can cause problems for your company. The list of issues is a good one, and worth reading through.

    There are a couple of items in the list that I thought were very interesting for data professionals. The first was the fact that companies need to ensure that they implement policy from the beginning for how cloud services will be used. I think this will always be a point of contention between IT and the clients, and this isn’t an excuse to lock down clients or limit their options. Instead it ought to be a place where IT looks to be informed, help with guidance, and respond more quickly to client requests. IT cannot be the stumbling block in the cloud, or it will get left behind.

    The other thing? This quote: Have the ability to bring things back internally or to another provider at any point. That’s a great point. The cloud isn’t the ultimate answer, and you ought to have a backup plan, which should include the ability to move your services back to your own data center.

    Steve Jones

    The Voice of the DBA Podcasts

  • Jobs for Data Scientists

    This is the trend line we like to see for database jobs

    I wrote about data scientists while back, which seems to be a field that involves the analysis of large amounts of data and the tools involved in this work. The definition of this area is a little nebulous, but that hasn’t stopped companies from looking for people to work in this area. There are jobs for data scientists, and perhaps for interesting, there seems to be more and more jobs for people to work with “big data”.

    This article shows a huge trend up in the “big data” keywords in job listings. That makes sense as I think the data growth has far outpaced the ability of tools to work with large datasets. Excel had a problem with large amounts of data until recently, and most of the other tools used are either very expensive or home grown.

    Many of the people subscribing to this newsletter are technical people, those that work to form the computer into a tool that someone else can use to do their job. It’s an interesting job, and one I hope you enjoy, but there are some of you out there that would like to do more with data than just find ways to help others query that data. Perhaps a data scientist is a job that you would like to move into at some point.

    This is an area that I suspect many companies will want to focus more efforts on in the future, and I think that being a DBA who knows how to query data and find patterns gives you a head start on moving into a position that can be challenging, fun, and perhaps most importantly, without much after hours work.

    If you like statistics, patterns, and helping your company actually make use of the information in data, perhaps a data scientist might be the position for you.

    Steve Jones

    The Voice of the DBA Podcasts

  • The Impact of Outages

    This is not what any of your clients want to see. So prepare for issues

    Are you going to start seeing more pressure for outages in applications? I suspect many outages are caused more by application issues than database ones, but those two are becoming very tightly linked as we look to more rapidly deploy features and enhancements in our applications, which often include database changes

    This outage from United shows that there can be a huge impact, not only financially, but also an inconvenience to clients and potential lost future business. A company might struggle to with future business after a large outage, especially when there are so many other choices easily available to consumers across the Internet.

    That brings to mind a very interesting problem as companies grow and look to build scalable systems. Large groups of servers require some level of standardization, mostly for the ease of management by IT workers as well as the ability to train future workers to understand the systems. However that standardization becomes a point of failure when there is a problem during an upgrade, or even a hack from some type of malware.

    I saw an interesting piece on how Netflix has tried to expect, and handle failures in the cloud, and a comment from Jeff Atwood that you ought have your own chaos monkey to regularly test your systems. Interesting advice, and in many cases, it’s probably good advice to ensure that both your systems and your people know how to deal with outages.

    You probably cannot eliminate outages, as Netflix and many other companies have learned. However you can work to ensure your people and systems know how to respond. I also wonder if having (at least) two versions of your systems out there at all times that work in a similar way might be a way to provide some tolerance against a single point of failure. I don’t know how you might implement this, but it might provide some protection against a failure in a completely homogeneous environment.

    Steve Jones

    The Voice of the DBA Podcasts