The following is a list of major articles written by Lee.
Migrating to the cloud is easy, right? What could possibly go wrong? There are at least four things I can think of.
Often, when we begin a cloud migration, we come in with lofty expectations. As the migration progresses, however, we often find that moving to the cloud isn’t necessarily as easy as we would like it to be - or as easy as we were led to believe it would be.
Traditionally, cloud has been positioned as a cost-effective method of hosting applications. While this mindset has led to some positive cloud migration cases and effective cloud-native application development, the opportunities go much further for ambitious businesses wanting to make the most of the move to the cloud. A cloud-initiated transformation within a business can be the mechanism for providing consistent customer experiences on a global scale.
What has often held companies back with cloud initiatives is a conservative approach to controlling data. But after more than a decade of lessons and established success the questions have shifted from “why move to the cloud?” to “how do I make the move successfully?”
If your organization is looking to modernize mission-critical applications and you’re planning a cloud migration as part of this process, you don’t want to repeat others’ mistakes. So this post leverages those learnings to build a 10-step checklist of the major areas you need to consider and address to maximize your chances of a successful cloud migration.
Cloud computing is mainstream. That’s a fact.
Chances are if your company isn’t already extensively using the cloud, it is planning on doing so in the very near future.
But be careful. There are many mistakes that companies new to the cloud make when they begin looking into cloud adoption. Here are three of the main ones.
Forget about AWS Lambda and Kubernetes – AWS Fargate is the real future of serverless because it’s containers that matter, says New Relic’s Lee Atchison.
There are two main ways that modern enterprise applications use the cloud. There’s the “better data center”approach to using the cloud, and then there’s using the cloud in a more dynamic fashion.
Where you live in the world changes how you feel about cloud adoption. New Relic’s Lee Atchison reveals five differences he encountered on three continents.
Whenever we discuss cloud adoption with enterprise companies curious about making the move, one of the first questions is, which is better: public cloud or private cloud? Cloud adopters want to know which approach is most likely to give them better performance, greater flexibility, stronger security, and lowest cost to operate.
While these are important requirements, they miss a critical issue: do you want to share your cloud with others? If you’re working towards an effective cloud adoption strategy, you’d be wise to consider whether you want a multi-tenant or single-tenant cloud offering.
For many enterprises, finding success in the cloud is still a daunting challenge. Too often, organizations set overly high expectations for the benefits while underestimating the amount of work required. An unfortunate result can be a vicious cycle of blame, finger pointing, and grasping for something—anything—that could be considered a victory.
Conventional wisdom says you should protect your data by keeping it close. In reality, it’s more secure with SaaS companies.
At New Relic, we talk a lot about the dynamic cloud. The dynamic cloud is the primary method of implementing a dynamic infrastructure, which allows enterprises to build highly flexible, highly available applications that can meet nearly any scaling need. But what exactly does it mean to be dynamic?
Ever wanted to know about serverless computing but were afraid to ask? New Relic’s Lee Atchison tells all and explains its impact on the digital enterprise.
Selecting Multi-Cloud Vendors in the Real World. This guide will help determine whether a multi-cloud environment is right for your app and offers some advice in choosing the right cloud model for you.
When migrating applications to AWS, it doesn’t matter if you are rehosting, replatforming, or planning a full refactor—as you take each step, you should know what’s working. Above all, you need to know if the user experience of your migrated app is what you expect it to be—especially at that moment when the workload has moved and everyone is watching.
How can you tell that a migration has successfully completed? How can you be sure that you haven’t introduced a problem or a looming concern into your application? How do you determine that you don’t need to do any further tuning or adjusting to ensure that your app that was previously running fine on-premises is stable and performing well in the cloud?
Ultimately, you can’t declare a migration successful until you’ve proven it works as expected in the new environment.
AWS Lambda v Amazon ECS on Docker containers. Which of these pay-as-you-go compute services is for you? New Relic’s Lee Atchison weighs them up.
Major bug? Human error? Neither. The AWS S3 outage last week was more like a minor bug in an otherwise solid availability plan executed by AWS.
Agile says build a minimum viable product (MVP) and continuously improve it with DevOps. Just don’t neglect architecture.
Isn’t single-tenant SaaS just managed hosting? New Relic’s Lee Atchison delves into the world of SaaS look-alikes to find the real thing.
Technological innovation drives every business, industry and sector - mostly positively, but not always. 2016 was no exception – from the first long-haul driverless cargo delivery to automated retail locations to the stiffening competition among ‘smart assistants’ we’re seeing big technological leaps at a breakneck pace.
How to make services just the right size.
Short video about mastering the transition from Static to Dynamic Infrastructure.
Article about the concepts I talk about in my book, and why I consider them important.
Blog article talking about our FutureStack16 event “across the pond”.
Blog article talking about the New Relic tech event at Fenway Park in Boston.
This is the second part of a two part series on microservice architectures, how they are used in application development and the role that APIs play within them.
This is the first part of a two part series on microservice architectures, how they are used in application development and the role that APIs play within them. The second part looks at what distinguishes a typical Web API that you might add to your enterprise from a microservice (with an API) and when the two approaches make sense.
We know the cloud is changing the way we think about computing. The cloud is changing the way we run our applications. The cloud is even changing the way we pay for our applications. The cloud is changing everything.
Dealing with monolithic applications often caused development organizations to get stuck in the muck, resulting in slower, less-reliable applications and longer and longer development schedules. The companies who create those applications, as a result, end up losing customers and money.
The muck is not inevitable. You can rebuild and re-architect your applications to scale with your company’s needs, not against it. Using a microservice-based application architecture is an increasingly popular technique for building applications that can scale without miring your organization in the monolithic muck.