Articles, tagged with DevOps, providing techniques, guidance, and best practices for how to build web applications that scale to significant traffic volumes.
Join me at the xMatter’s Flow 18 conference on October 22-24 at the Radisson Blu Aqua Hotel in Chicago, where I will be giving one of the keynotes for the conference. I will be giving my newly created “Keeping Modern Applications Performing – Driving Insights to Action within the Enterprise” talk, where it will make its North American debut. This will be hot on the trail after giving it down under in Sydney and Melbourne Australia the week before.
Microservices is a hot topic in software development circles these days. And for some very good reasons. Put simply, the traditional way of building enterprise applications—using a monolithic approach—has become problematic as applications get larger and more complex. So developers are turning to a microservices software development architecture, in which applications are structured as collections of loosely coupled services. This makes them easier to build, and—more importantly—much easier to expand and scale. Let’s take a closer look at how a microservices approach differs from a monolithic one, and examine their relative strengths and weaknesses.
On July 17th, I was fortunate enough to take part in a podcast jointly sponsored by Electric Cloud and DZone titled “Continuous Discussions: The DevOps Toolchain”. The podcast was a panel discussion with a variety of DevOps experts from around the industry. I was fortunate enough to be included on this panel.
The #1 book on their list is “Architecting for Scale” book by Lee Atchison. As the article says:
“The yin-yang of dynamic apps and DevOps may come into a new balance in 2018. Container orchestration will be less important, while monitoring live deployments will become the crucial focus. This shift comes in large part due to big steps in Amazon Web Services, says Lee Atchison, senior director of strategic architecture at New Relic. IDN explores. “ Read this interview with Lee Atchison on idevnews.
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.
As applications grow, two things begin to happen: they become significantly more complicated (and hence brittle), and they handle significantly larger traffic volume (which more novel and complex mechanisms manage). This can lead to a death spiral for an application, with users experiencing brownouts, blackouts, and other quality-of-service and availability problems. “But your customers don’t care. They just want to use your application to do the job they expect it to do. If your application is down, slow, or inconsistent, customers will simply abandon it and seek out competitors that can handle their business. That’s how my new book, Architecting for Scale: High Availability for Your Growing Applications, begins.
I had the rewarding opportunity of being a guest on theCUBE on Silicon Angle TV at the AWS Summit in Santa Clara, CA.
I was interviewed recently by O’Reilly Media about my book Architecting for Scale. This interview was recorded during the O’Reilly Velocity conference in Santa Clara, CA, on June 23, 2016.
Software Engineering Daily Podcast. Listen to Jeff Meyerson talk to Lee Atchison about Lee’s new book, “Architecting for Scale”, by O’Reilly Media.
What a great day!
On Tuesday, July 5, we officially expanded our annual FutureStack user conference beyond San Francisco, kicking off our new FutureStack16 Tour “across the pond” in London.
Take a look at the article
Customer Successes Take Center Stage at FutureStack London,
I wrote that shows what a truly great day it was.
I arrived at the hotel, a typical Residence Inn, and checked in. “You have a view of Fenway from your room”. Oh, that’s cool. I went to the room, looked outside, and there she was, the green industrial looking complex that is Fenway Park. It didn’t look all that special from where I was. That would change. I arrived early in the day, and didn’t “officially” have any scheduled events until the next day, but I had to prepare what I was going to do the following day, and I’m sure I would be meeting up with some of the other New Relic and MLB folks for dinner later. But, that still left me time to look around.