Container orchestration services are becoming more and more popular, as teams are looking to run their container workloads at scale. Kubernetes is already extremely popular, as well as the managed orchestration services by the cloud providers. In particular, AWS’s ECS and Fargate, are commonly used among AWS users, often combined with Lambda functions and other AWS services.
In today’s data-rich world, data products that turn data assets into actionable insights are becoming increasingly valuable. Technologies that help users surface, process, organize, store, share, and act on data have defined a new generation of products. That’s why we sat down with Katie Bayes, a product engineer at IOPipe. Katie has deep experience designing data products, and her advice will prove valuable to any teams designing data products.
There is a new hype in the DevOps world: Istio and service meshes. But why exactly is everyone suddenly migrating to Istio? In this post, we will examine whether it actually makes sense to use Istio and in which use cases it may help you (as well as when it’s simply an overkill). But before discussing Istio, we should first introduce the concept of a service mesh.
Amazon recently announced EventBridge to much fanfare. Although, in truth, it’s a rebranding of the existing CloudWatch Events service, along with some new features. But rebranding might be exactly what this old dog needs!
In traditional applications, security misconfiguration can happen at any level of an application stack, including network services, platform, web server, application server, database, frameworks, custom code, and preinstalled virtual machines, containers, or storage. Luckily, almost none of that has anything to do with serverless. The network services, platform, database, frameworks, VMs all of that belongs to the cloud provider. Containers? We’re passed that. Servers? What are those?
Intelligence is the ability to adapt to change. These are the words uttered by the great Stephan Hawkins and can justly encapsulate the core meaning of the Agile concept which has revolutionized the way we conceptualize and produce software. The tech industry has gone through sweeping changes that have resulted in expeditious software production. Gone are the days where software teams would spend months and even years to deliver on new features to improve the experience of their customers.
In 2016 I was the tech lead for a greenfield project completely devoid of legacy–I held the engineer’s promised land in front of me! I bit off as much new stuff as I could – serverless, event sourcing, functional programming, the whole gambit of cool. This is normally a very bad idea, but I had a team of strong engineers who had prior experience in this stuff, and we were ready to be technology pilots for the broader organization.
Digital performance is the new normal. Every business wants and needs to deliver optimal digital performance across all kinds of applications for employees and customers alike. Apache OpenWhisk For example, Adobe introduced the Helix project—“the new experience management service to create, manage, and deliver great digital experiences.” Adobe is using Apache OpenWhisk as part of their Helix project.
Every day that I commute home, I check Google Maps for the next Trimet bus arrival at the usual stop. There’s nothing wrong with this ritual but it always distracts or leaves me stalled for a few empty minutes. Ever the proponent of laziness automation, I decided to build a stack that will do this for me by texting incoming arrival times for my bus home.
We are going to talk about an essential part of AWS Lambda called “AWS Step Functions.” What are Step Functions? Why are they important for AWS Lambda users? What are they used for, and what can we expect to get by using them? Bare with us, and discover more critical information on Step Functions throughout this article. We’ll begin with the explanation of what are Step Functions. AWS Step Functions service is the most recent service released by none other than Amazon Web Services.
