Building Serverless applications isn’t very different from building traditional software. We need all the same pieces of the software stack: The UI, API, and Database. Previously, we talked about the serverless technology used to build the API. Now we are going to take a look at the most common serverless technology used as a Database: DynamoDB.
As developers there is one aspect of starting a business that seems to trip most of us up. That is the process of finding an idea to work on. We spend a lot of energy trying to imagine a problem to solve, and then even more energy building the solution to our imagined problem. If we ever actually build and launch these solutions, they fail.
One of the biggest buzzwords in the software industry right now is Serverless Architecture. Unfortunately, there is a little ambiguity about what the term Serverless actually means though. In this article we will examine the two different (but also overlapping) definitions of Serverless.
Most applications will require a way to store data that persists between sessions. When the user starts the application, we need a way to retrieve the latest data. The way the client interacts with the application is called the Application Programming Interface, or API.
The Microservices Architecture is a popular style for designing large complex systems.
Are you looking to build a Micro-SaaS (or a regular SaaS) business but don’t know what language to build it in? Unlike what some developers believe there is not
One Language to Rule Them All, so you can’t make a wrong choice. You can however, make your life much easier if you know the tradeoffs of each language. Consider the following tradeoffs when evaluating a language:
The idea of the Micro-SaaS captures my heart and I love it. I am not a huge fan of the name, but I can live with it since it is how most people refer to the concept. (I prefer the name SaaM - Software as a Microservice) I am always analyzing the world around me and I come up with a lot of neat ideas. The thing is, ideas are cheap. They mean nothing unless they get executed and execution is where I can’t do them any justice. So, I want to start throwing ideas out and hoping that someone takes one and runs with it. The only thing I ask, is if you end up building an awesome thing with one of my ideas, shoot me an email so I can do a little happy dance for you! Without further ado, here are my Micro-SaaS Ideas for March 2017:
It’s that time of your again… time to interview the next batch of hopeful interns. And just like every year previous, I am sorely disappointed in the quality of candidates that are showing up. I work for a company that isn’t one of the top 5, but we are definitely highly respected and consistently rank in the top software companies to work for on sites like Glassdoor. So, we should be getting interns from top tier institutions.
How do you come up with an idea for a SaaS company? I have asked myself this question multiple times and have struggled to put the answer into words. I have worked at several SaaS companies and they all seem to start in a similar way. The founder is looking for a solution to a specific problem they have. They either can’t find a solution, or they find one at a crazy price they are unwilling to pay. They decide that they could do better just to build it themselves and viola, the seed of a SaaS startup is planted. I just planted such a seed and I want to share with you the line of reasoning in case it helps inspire anyone else looking for inspirations in the world around them.
For those that don’t know, I am a huge supporter of all things AWS. I spent 3 years working at Amazon building amazing things on top of AWS and have spent the years since doing the same at Genesys. My career didn’t really begin to blossom until I started to fully embrace the power of Amazon’s IaaS services. They have released a lot of best-in-class tools to allow developers to really build some amazing things. That is why it always saddens me when I come across a tool that doesn’t live up to my expectations. And it is with a heavy heart that I pronounce CodeCommit as a giant pile of shit.