It’s the beginning of a new year and when it comes to computing, going serverless is the resolution of many engineering teams. At Stackery, this excites us because we know how significant the positive impacts of serverless are and will be. So much, in fact, that we’re already thinking about its applications for next year and beyond.
What a year! It started with just me and Mikk, hacking away at our homes with an MVP and a handful of customers. Now, Dashbird is a team of 6 people with a lot of customers, global investors and a vision for the future. Looking back at the year, we’ve had a lot of wins and also our fair share of failures/learning experiences. I’m very excited for the upcoming year, but before we get into that, let’s look back at the year that just ended.
Whether you are just migrating to Google Cloud Platform (GCP) or have well-established workloads running, monitoring spend is essential to maximizing your investment. As of a recent release, you can monitor GCP spend alongside resource performance with LogicMonitor.
Pharmaceutical companies are witnessing a shift in the way they function where innovative products, beyond the pill concepts, automated machine systems, etc. are defining new boundaries. Eroom’s law acknowledges the fact which states the cost and time taken to develop a new drug almost doubles every nine years.
As the CEO of Stackery, I have had a unique, inside view of serverless since we launched in 2016. I get to work alongside the world’s leading serverless experts, our customers, and our partners and learn from their discoveries. It’s a new year: the perfect time to take stock of professional progress, accomplishments, and goals.
Multi-cloud is a cloud computing strategy that uses two or more different cloud services. This can be a combination of Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), or Infrastructure-as-a-Service (IaaS) solutions running in a public or private cloud environment. Multi-cloud offers a number of benefits including greater reliability and availability, less vendor lock-in, and potentially lower costs.
Already have a monitoring service with your current host? Does your plan include Amazon CloudWatch, Azure Monitor or another proprietary monitoring tool? You might want to check the fine print. These services often provide internal web monitoring only. While they may check HTTP availability from locations outside their network, HTTP checks alone are not sufficient.
If you missed the first 2 tips, go back and read 5 Tips to Avoid Deadlocks in Amazon RDS (Part 1), and then come back for the last 3 tips on deadlock avoidance. Once again, I want to re-emphasize that RDS is not actually capable of creating deadlocks — it merely reports them from the underlying database engine.
Over the last couple of weeks, we’ve prioritized some sustaining product goals to polish the codebase and update some big ticket dependencies. Among those updates were: React, Redux, and Webpack - the biggies. The first two were pretty painless and inspired the confidence to approach updating Webpack from v2 to v4 like maybe no big deal! Though confidence level was on high, I felt a slight chill and a twinge of doubt by the prospect of making changes to our build configs.
