Serverless design patterns
When developing Serverless applications, you can use different architectural design patterns depending on the project’s use case and goals.
When developing Serverless applications, you can use different architectural design patterns depending on the project’s use case and goals.
A summary of the best re:Invent announcements related to Serverless
A summary of the 'Shared responsibility' and 'Principal of Least Privilege' sections from my book
A summary of the 'Estimate and track operational costs' sections from my book
A summary of the 'Cost to develop Serverless' section from my book
A summary of the 'What is Serverless architecture' section from my book
In this article, I explore how we can run a truly serverless docker container on AWS.
Serverless architecture lends itself well to tracking costs and linking them back to specific users.
What is the difference between a solution architect and an enterprise architect and why both are important.
Here are a few ideas you can consider if you are embarking on an innovation transformation journey with your business.
I spent a week in Cambodia with Slash training their team serverless and launching the first AWS User Group Cambodia meetup.
An overview of some of the different types of microservices I have used in my projects (on AWS Lambda).
I recently found a potential attack vector related to serverless, after some research it seems quite plausible but, fortunately, limited in cost risk.
Evaluating technical contracts and vendor negotiations can be tricky for non technical people, but some of the business terms could be confusing even for seasoned technical experts.
Online privacy is a complicated, sensitive and increasingly regulated area.
In this article, I take a closer look at the more strategic impact of serverless architecture.
Grants don’t come easily, and knowing how to source for them increases your chances of getting your ideas off the ground.
Relationships can be hard work and when money, deadlines and complex technical requirements are involved they can be even more of a challenge.
An essential part of scoping projects, this article seeks to explain what they are and why they are important.
Recently, I finally published a book I had been working on for some time, I want to share my experience with this adventure.
In this article I cover the 3 most common project management approaches to scoping and how my approach uses the best parts of each while minimizing the negative aspects.
Detailed and meticulous scoping and research for your custom web or mobile project will ensure you are well prepared for development, but it does not stop there.
From time to time we get asked by clients if we can draw up a comparison chart between Off The Shelf and a custom solution.
The kick-off for all projects is a lengthy but structured discussion between all stakeholders and a consultant to get detailed insights into their goals and requirements for the solution.
Businesses believe that mobile apps will enable them to reach out to more users and customers but often underestimate the challenges involved.
Working for equity can be a way to gain valuable experience for junior or freelance developers, but if you are looking for more than just experience ask the right questions and be aware of the risks.
Most of the computer-literate public today suffer from “app burnout”. No matter how useful or entertaining your new app is, the average smartphone user hears about a dozen new “killer apps” each week.
Before embarking on any major project it is essential to do research to confirm and validate the project and its requirements. This research can help shape the plan to ensure maximum chance of success with the target audience.
If you are in the creative industry, it is common for clients to ask for a new website, or web or mobile application. You may have a few ideas - but are they possible?
A hierarchical approach to business teams might work for the banking industry, but far more productive results and increased innovation can be achieved with a dynamic approach to project teams.
Lately most of the projects we have been doing Solution Architecture for have been serverless. But what does this mean exactly and what makes it so great for web applications?
We are frequently approached by prospective clients who think they need a custom website. More often than not, we recommended these clients to start with a subscription platform.
Many inconsistencies between estimates and final invoices can be improved with a better approach to vendor briefings. This approach can even follow corporate procurement guidelines.
A large part of what we do is educating people on all matters relating to custom application development and we have noticed that there are a few misconceptions that many of our clients share in this area.
Where does this fixation for fixed price come from, why is it so prevalent in the tech industry and why is the concept of fixed price completely counter-intuitive and flat out wrong?
How you can build better applications by focusing on users’ requirements instead of technology to drive decisions in your application planning.
A loaded question with different answers from different people. This article is about bugs in custom applications, my opinion on the matter and how to reduce the frustration they can cause.
A more in-depth look at the contents of our Solution Architecture documents and insight into the areas we evaluate and research when writing them.
Many clients embark on the journey that is custom web/mobile application development full of enthusiasm and with clear goals and deadlines in mind. But more often than not, this quickly turns sour.
To get the best possible estimates you must ask the right questions and manage both your own and the vendors’ expectations. But which questions should you ask and how to ensure that you get consistent estimates from multiple vendors?
Through my work and network I have helped many people who wanted a new website or web application but were unsure what to do next. Many of them started by looking for a designer or developer and getting an estimate.
Binary Thinktank no longer provides development services but focuses entirely on Solution Architecture. But what is SA? And how come there is enough of it for a company to only offer this?