I’m on the og-aws Slack group, one of the more active groups of AWS developers and cloud practitioners. A member of the channel, Samuell, asked a question about S3, Cloudfront, and new files, and I saw the perfect opportunity to help out, so I offered.
Most Rails developers should be pretty familiar with this work flow: open up a controller file in your editor, write some Ruby code inside an action method, visit that URL from the browser and the code you just wrote comes alive. But have you thought about how any of this works? How did typing a URL into your browser's address bar turn into a method call on your controllers? Who actually calls your methods?
As more enterprises host their applications in the cloud, it becomes increasingly important for application performance monitoring (APM) solutions to ingest performance data pipelines from cloud providers.
Recently, Toshok was telling a story about the kind of thing he talks about a lot—improving the performance of some endpoint or page or other. Obviously, we spend a lot of time thinking about how to improve the experience of our users, but what caught my attention this time was that what he was describing sounded like a new kind of testing in production—so I asked him to go into a bit more detail.
It’s not just our customers who choose our technology time and again. BigaPanda is also recognised by the industry as an innovator whose cutting edge solutions provide Enterprise IT with both value and innovation. We’ve been named one of the 10 finalists for The MIT Sloan CIO Leadership Award in the MIT Sloan CIO Symposium Innovation Showcase, and one of the 30 Best Companies of 2019 by CIO Bulletin.
Last year we covered the top enterprise serverless use cases for AWS Lambda. To refresh our memory, according to the CNCF (Cloud Native Computing Foundation), most commonly AWS Lambda is used for REST APIs, multimedia/image processing, CRON jobs, and stream processing. Today I’d like to cover some more complex ways some of our enterprise customers use Lambdas.
No matter how carefully coded, reviewed, and tested your Ruby code is, odds are good that at some point you’ll cause a catastrophic failure to at least one system you’re responsible for. How do you prepare yourself? You need a Ruby debugger. In this post, I’ll cover the whole Ruby debugger process—from finding the issue to determining the root cause. Use these instructions for debugging a single Ruby file, a Rails app, or a gem.
If you work in tech, you’ve probably heard that “team culture” is the most important thing for a successful organization. Camaraderie, trust, passion… a good team should have all that. And it’s hard to deny that loving the team you work with will make you more successful, but how do we build that? There’s no AWS product called TeamFront and it’s not sold on Amazon. How can we take camaraderie from elusive to undeniable?
Having a fast website is something that used to be great to have, but today it is literally a requirement. Slow websites affect your site in both terms of search engine ranking as well as your visitors’ attitudes. 47% of website visitors expect a site to load in less than two seconds.
We all want to ship code on a daily basis. As developers, we want the faster feedback cycle that comes with continuous delivery, and we know it’s better for our team and product in the long run. So why do so many development teams still have such long release cycles? While long release cycles are tried and true and can be seen as more stable, teams sacrifice much more than faster feedback cycles.
