- Expert Mentors
- How it Works
- Become a Codementor
No rating yet
For every 15 minutes
MySQL DBA, Amazon Web Services specialist, and Perl developer based in Cincinnati, Ohio.
Indiana (East) (-05:00)
- 15 years experience
Since I discovered Perl in the late 90's, It's been my typical tool of choice for automation and administrative scripting, but my current company's entire web stack is Perl-based, including our own in-house proprietary Perl web framework ("Chameleon") so I have been developing extensively in Perl for the past 3 years.
- 5 years experience
I've been exposed to MySQL for maybe 10 years, but I've been working with it extensively for the past 5, and I've officially been a full-time DBA with my current company since early 2011.
- 2 years experience
Our company began "testing" AWS in 2012. We fairly quickly starting migrating services out of our physical data center and into AWS. We use a number of their services and I am one of 2 AWS admins. I prefer being "closer to the metal," so I prefer working directly with their REST APIs rather than relying on their SDKs or 3rd party libraries... most of the code we use is our own homebrew.
- 15 years experience
I've been administering Linux servers since 1.x kernels in the late 1990's. For many years, I worked with Red Hat/CentOS, but within the past 3 years it's been primarily Ubuntu. I have experience with various flavors of Solaris and Windows servers as well, but they aren't my platforms of choice.
- 3 years experience
Mojolicious is an asynchronous, non-blocking, event-driven web framework for Perl that makes writing the client connector or server components of APIs extremely straightforward. In addition to writing AWS API libraries in Mojo, I've developed other tools such as my "second tier" reverse web proxy that attempts to fetch each request from a primary http server and return it to the requester -- if the request fails (for example, 404 Not Found) the proxy will try a second server for the same URI. If the second server returns success, the object is returned, otherwise the primary server's error response is returned. This allows 2nd tier/low priority/rarely requested resources to be stored on a second server, but to be served up from within the primary server's URI name space.