This post is part of our Cloud Exit series. Over more than a decade we paid AWS about $244K, net of credits. Then we rebuilt on servers we own. Earlier posts cover the full cost story and how we swapped Lambda for cron. This one is about the database, and why moving it was the easy part.
Everything our 97 Lambda functions used to do now runs as a handful of Python scripts on a schedule, on servers we own. The SQS queues are gone and so are the SNS topics. When something breaks, there's one log file to read, not a chain of request IDs across five services. And the bill dropped fro...
Buzzwords worked. It read the news from dozens of sources, pulled out the words everyone was repeating, scored the mood of each channel, and told you what the world was talking about today. It started as one cloud function in August 2016 and grew into a real event-driven platform: 32 Lambda funct...
In 2019 we paid Amazon Web Services an average of about $4,500 a month. Today our infrastructure runs for about $100 a month, on hardware we own.
Our infrastructure now costs about $100 a month to run, on hardware we own. A few years ago, the same company was paying Amazon Web Services an average of about $4,500 a month. In 2025, with most of the move behind us, the cloud bill was still a few hundred dollars a month. Today the cloud is a s...
In this post we will discuss the key parts of a well architected aws codepipeline, and what that looks like.We will break apart an existing pipeline, and use some ninja commands and methods to put it back together better, including scaling pipelines horizontally to assemble enterprise grade stacks.We will also add some controls for governance & approval mechanisms to ensure successful & true CI/CD with our 100% native AWS CodePipeline.This article is a sub-section of the bigger topic & Series: T
In this post, we will focus on some of the important layers of the buildspec.yml file, in order to assemble our stack and it's layers the right way, like constructing a delicious application cake ;-) Let's begin...[TODO]link to official docswriteup about runtime section, pip / node install sections, sed parameters.json files, and the important artifact section....
In this chapter, we will review the anatomy of an AWS CodeStar project and all the plumbing that comes with it, including the structure of t
In the following series, we will explore how to setup a well architected cloud software project in the AWS cloud, from beginner to advanced,
Screenshots & code examples of monster horizontal codepipeline.
In this article, we will learn about AWS CodeStar - arguably one of the most important aws cloud developer tools that most Cloud DevOps engineers are not even familiar with.We will get started with some example AWS CodeStar code & architecture patterns.We will provide links to examples throughout the article.Let's begin! View Our Ai Explainer Video about this post!!Like, Comment, Subscribe to our YouTube Channel, for more Ai explainer videos!What is AWS CodeStar?Think of CodeStar as a wrapper se
The problem is, you don’t know what good looks like - till you either a) see good with your own eyes and/or b) make all the mistakes possible till you figure out what good looks like on your own, based on all the good, the bad & the ugly that you built yourself…((and then comes the over / re- engineering problem but that’s a different blog topic…))As for me?…all of the above…i made the ugly, painful mistakes, then after lessons learned, started to build the right way, and was fortunate enough to
Branching / Tagging Strategy and Git Flow from an AWS DevOps perspective using native AWS CI/CD AWS CodePipelin
Because browser based IDEs are the best ;-)ok, seriously, let's elaborate....why do i prefer AWS Cloud9 IDE over local IDE? a few reasons:SECURITY* Cloud IDE is provisioned & protected & governed within the specific company cloud perimeter & security controls. * when the dev env lives within the project in the specific cloud account, it is the most secure and easiest to lock down & secure in case of a breach or termination.* less code leaks from local insecure or stolen laptops / workstationsRES
Introducing the new shiny :: * https://buzzwords.newsNew Features:* More Speed!* More Precision!* Visualization! Motivation:* To measure every word mentioned in todays digital media* Based on this, to calculate the positive / negative sentiment at scale* To hold the media accountable* To gain back wasted time reading through infinite feeds of duplicate / recycled news content Goals:* Precision calculation at scale* Perfecting AutoScaling & ServerLess* Maintaining maximum compute cost efficiency*
SEO has caused de-innovation...why? cause we wasted time building web apps to serve the robots, and the crawlers, and "the google", and bing? ;-/ && the hackers...SEO has killed innovation...why? if it weren't for paths and routes, single page pure javascript applications would rule, we wouldn't have to build in routing logic into our web applications to handle goofy outdated things like URL paths and we could load things on the fly into the DOM just based on click & touch events, swapping out d
Introducing, ServerLessJS.io , a simple, open source framework for developing serverless decoupled applications based on pure html, javascript, css on top of serverless AWS Cloud Architecture: Fork Me :: https://github.com/StabilityFocus/serverlessjs.io See it in action:* https://serverlessjs.io* https://fe.buzzwords.news* https://thatsawesome.org
the essentials of a javascript framework:* code organization* templating / theming - seperation of code logic & render* routing - path / parameter / route handling ** the damage SEO has done to Single Page Applications
I am a big believer in Keeping It Simple...life as a Tech Entrepreneur has taught me that over-engineering has a big cost, so i am going to outline a simple method to Progressively Decouple Drupal, The Easy Way!...using pure javascript & html, using a small code snippet, inside an existing Full HTML Drupal Editor Body, out of the box Front End Drupal functionality, without the need to write an actual module to load your javascript in the backend with P
Today is an exciting day for me....after years of hard work, i have reached a milestone......i have finally reached "The Coupling Point" ™ The Coupling Point, is the point in your application integration, where you can merge 2 different technologies together, for the purpose of creating a better experience for your application users, and for me, most importantly, how to make your application more efficient for the purpose of cost savings on your application architecture to reduce cloud infrastru
Super App:* WixUI* pureJS fe libs with Serverless backend* d8 rest api or json api
These cookies enable core functionality such as security, verification of identity and network management. These cookies can’t be disabled.
These cookies are used to track advertising effectiveness to provide a more relevant service and deliver better ads to suit your interests.
These cookies collect data to remember choices users make to improve and give a more personalised experience.
These cookies help us to understand how visitors interact with our website, discover errors and provide a better overall analytics.
