This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
After all, we’ve been doing that forever with the 2nd-level cache of ORMs , and it is highly encouraged in e.g. the AWS Lambda programming model — which was born on the cloud— to help mitigate function start-up times. The network latency of fetching data over the network, even considering fast data center networks. Who knew! ;).
In the 2000s we had a showdown of two popular blog publishing platforms — MovableType in 2001 and WordPress in 2003. In addition, they introduced a hosted version of MovableType in 2003 called TypePad to compete with other popular cloud platforms. Twitch developer documentation hosted on AWS, edited on CloudCannon.
Clouds using Ethernet that are multipath optimized using libfabric and features like EFA on AWS are going to be increasingly competitive, and Ethernet will replace other interconnects between racks. I presented a keynote for Sun at Supercomputing 2003 in Phoenix Arizona and included the slide shown below.
The term site reliability engineering first came into existence at Google in 2003 when a site reliability team was created. One minute an SRE might be provisioning storage in AWS, the next minute an SRE might have to talk to customers or go write some Python code for a new project. Monitoring. Incident Response. On-call Support.
In 2003, Gregor Hohpe and Bobby Woolf released their book Enterprise Integration Patterns. AWS, Kafka, Google Cloud, Spring, ElasticSearch). Orchestration tooling was also not ready for SOA, with manual deployment scripts being one of the most common ways of deploying new versions. The rise of enterprise integration patterns.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content