Ease of use is almost more important than the actual function to many. The reality is that there is a much stronger business case in most instances to providing this data in a metered self-serve format. At one time, however, business culture viewed this kind of exposure as “giving away the farm” - why would you expose a critical business function that generates revenue in a public form? Is it not better to have agents handle this data on a case-by-case basis to extract maximum value? Users can leverage the interface and its internal functions to do more with less handholding. On the one hand, providing business functionality through an interface seems like a pretty clear win. While this seems like a no-brainer for API developers, there was a time where this was not the norm.īusiness functionality is an interesting beast. Interfaces allow for transmutability, bi-directional interaction, and leveraging within other systems, not to mention increased discoverability. Then, it’s no wonder that the first part of this mandate is a demand to provide this functionality through a service interface. The foundational agreement for an API provider is to provide access to a function through an interface. All teams will henceforth expose their data and functionality through service interfaces.” Nonetheless, the lessons imparted are essential, and as such, we’re going to discuss them with the assumption that the memo did exist in the form commonly shared. Let’s dig into each of these points (with the exception of 6 and 7, which are more cheeky than API-minded) and look at why they may be important, generally speaking.īefore we do so, it’s important to mention that this memo is often unattributed - the original source seems to have been lost to time due to the shutdown of Google+ (for an early reference, see this post by API Evangelist). This mandate helped encourage a lot of Amazon’s thinking around AWS, externalized infrastructure, and business-to-business functionality. Anyone who doesn’t do this will be fired. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. All service interfaces, without exception, must be designed from the ground up to be externalizable. HTTP, Corba, Pubsub, custom protocols - doesn’t matter.ĥ. It doesn’t matter what technology they use. The only communication allowed is via service interface calls over the network.Ĥ. There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. Teams must communicate with each other through these interfaces.ģ. All teams will henceforth expose their data and functionality through service interfaces.Ģ. For many reasons, it’s become somewhat legendary in the API/microservices space, as it formed the basis for much of the modern API design paradigm within the corporate view. The mandate in question was issued in 2002 to Amazon by founder Jeff Bezos. We’ll dive into each point’s specifics and look at how the mandate formed much of the modern thought around APIs and microservices. This mandate would serve to form the backbone of Amazon in the modern web space, informing both the API development paradigm in the corporate mindset and a general improved approach to externalizing API functions.īelow, we’ll talk about the mandate and discuss why it has become so legendary in the API space. He was promoted to AWS CEO in 2016.In 2002, according to tech legend, a mandate was issued by Amazon founder Jeff Bezos. He has been at AWS since its earliest days, helping to build it from the initial idea to a $50 billion juggernaut.
DAY ONE AMAZON SERIES
Jassy joined Amazon in 1997 and spent some time working as Bezos executive assistant and helped formulate the idea that would become Amazon Web Services, a series of integrated web services. Well, it is actually Day 1 for his successor Andy Jassy, who officially moves into the corner office at Amazon today.īezos announced in February that he would be stepping down as CEO to focus on other interests, including his charities Day 1 Fund and the Bezos Earth Fund, Blue Origin, the billionaire’s space company and The Washington Post, the newspaper he bought in 2013.Īs he steps away, he will remain as executive chairman, but it will be Jassy, who up until now has spent most of his career at Amazon building the tremendously successful AWS cloud infrastructure arm, to keep a good thing going. Amazon founder and CEO Jeff Bezos has always liked to motivate his employees by saying every day is Day 1.
0 kommentar(er)
