DESIGNED TO SIMPLY DELIVER

Size: px

Start display at page:

Download "DESIGNED TO SIMPLY DELIVER"

Jared Manning
5 years ago
Views:

1 TECHNOLOGY DESIGNED TO SIMPLY DELIVER Mozu is on a mission to simplify delivery of the modern enterprise commerce experience through innovative technology solutions.

2 Table of Contents Intro / 3 Customization / 4-6 Server Side Programmability Front End Templating Complex Routing and Reverse Proxy Custom DB Schema and Extensions Customize Business User Tools Integration / 7-8 Open API Multi-Platform Developer Support Regular Updates / 9-10 API Contracts Beta Environment Unlimited Sandboxes Scaling / Internal Software Stack Architecture Instance Isolation Dynamic Scaling Distributed Cache Event Publishing Open Source Applications Developer Tooling Mozu Technology 2

3 INTRODUCTION Mozu is the first modern, truly multi-tenant Saas Enterprise Commerce Platform built in the modern mobile era on an open, micro services stack. Following are the principles that drove Mozu s construction and the architecture that emerged from it. Mozu Technology 3

4 CUSTOMIZATION Enterprise retailers need a platform that will allow them completely and cost effectively customize their commerce experience. Server Side Programmability in the Cloud In addition to building Mozu API first and exposing all business and storefront functions to developers through the REST API, Mozu also enables server side programmability in the storefront and in the micro service based API through Arc.Js. Implemented in Node.Js, Arc.Js packages have access to leverage the full Mozu API, HTTP protocol level operations, as well as the thousands of NPM packages contributed by the vibrant Node.js community. That means your developers can stand on the shoulders of community contributed code and are free to focus on the customizations that make retailer s businesses unique. Arc.js is at the core of how Mozu uniquely offers a truly multi-tenant Saas platform with modern development tools and the power to customize each implementation as if it were running on-premise. With Arc.js, developers can: Take control of critical business flows Augment existing business logic Replace entire Mozu operations with custom implementations Pre-process and post-process storefront and api requests Implement custom front end Hypr tags When coupled with the custom storefront routing engine, develop new routes and bind them to completely custom logic Mozu Technology 4

Modern Front End Templating Engine Mozu s storefront templating engine provides a strong separation of concerns between front end rendering logic and core business logic, allowing for rapid iteration

5 Modern Front End Templating Engine Mozu s storefront templating engine provides a strong separation of concerns between front end rendering logic and core business logic, allowing for rapid iteration on the look and feel of digital experiences. It s responsive out of the gate so implementing mobile and desktop optimized sites is no longer a technical challenge. You gain full control of every page of your site. The Hypr templating system is an isomorphic templating engine that allows for server or client side rendering depending on the needs of the page. Additionally, the language can be extended with custom tags using Arc.js for server side tag rendering. Hypr provides easy hooks into the SiteBuilder site editor visual tool set which allows template authors to define how business users can manage the content, layout, and look and feel of pages on the site. Developing for the Mozu cloud feels very natural with Mozu s client side build tools which allow for automatic synchronization and deployment of modified code assets into the Mozu sandbox environment no clunky manual file upload operations are required to quickly see the results of code as it is changed. Complex Routing and Reverse Proxy Because organic traffic is so critical for many retailers it is exceptionally important for retailers to have full control over the url structure of the storefront. Mozu s custom routing engine allows full control over url formats and parameters through configuration and also provides sophisticated redirect capabilities through rules and explicit matching. In addition, Mozu offers a Reverse Proxy service where existing investments in other online properties (such as a blog) can be retained but have requests resolved for all properties under a single domain. This provides further SEO optimization by keeping all content under the single domain and driving traffic to one online property. Mozu Technology 5

6 Custom DB Schema and Extensions Every retailer brings unique aspects of their business to the commerce experience and often this requires custom data to be stored, related and retrieved. Mozu has several mechanisms to achieve custom db schema in the commerce experience, all managed and accessed through the API and available throughout the platform. Custom Attributes on existing entities Create new properties on existing entities which can be typed, provide a vocabulary, and basic validation through configuration. Metadata Append open ended values to entities, no validation or typing. Catalog Types and Attribution Robust product classification with fully schematized types which include property definitions, vocabularies, validation. Product types become templates that determine which properties are required for different types of products. Custom CMS Content Types Traditional CMS metaphor for custom document creation: document types, document lists, content types, property types, etc Custom DB Entities Create a completely custom entities including indexes, optional schema, and sort and filter parameters. Customize Business User Tools Retailers can customize site and page management tools to give the amount of control they desire to business user when maintaining the site experience. Hypr allows for custom page settings as well as a robust widget framework for creating reusable and customizable bits of site functionality (and the business tooling to manage the functionality). This allows enterprises to give merchants exactly the appropriate amount of control over the site that they desire in screens that are optimized for their use cases. This widget framework is available not only to technology partners that want to build widgets for multiple clients but is accessible enough for developers for an enterprise to easily use for their own custom site management tools. Additionally Mozu allows for UI integrations with third party applications so users can access functionality across platforms without having to fully leave a single management console. Mozu Technology 6

7 INTEGRATION Enterprise retailers need a platform that can easily integrate into their commerce ecosystem Open API The backbone of Mozu is the REST API which exposes 100% of the functionality available in the platform. The API was developed first as the single point of access and not as an afterthought, and since all business user tools and storefronts are built on the same API that is made available to developers you are guaranteed that the API is feature complete and well tested. Mozu s API is implemented as literally dozens of micro services that each perform a specialized function. And because it is open and granularly implemented, developers have the ability to implement customizations within the services to gain the control they need over the administrative and site experience. And because all functionality is expressed through the API developers can integrate or customize in one place and be assured that no matter how the functionality is accessed their customizations will be executed correctly. Multi-Platform Developer Support The Mozu Api is accessible as raw REST resources or from one of our platform specific SDKs (Java, c#, php, Objective-C/Swift, Android, NodeJS, Javascript). All of our SDKs are released open source and available along with many other applications and code assets at Additionally all our build tools are cross platform and allow for local development to be completed in the IDE of choice for developers. We want to eliminate friction for developers and keep them in tools and languages that they are comfortable with. Mozu Technology 7

8 Event Publishing Mozu supports a robust event publishing system that allows applications to subscribe to specific business events that occur in Mozu. Every entity in Mozu supports the basic create, update, delete events in addition to a whole host of business process specific events for other system actions. The event system is also a REST based contract which allows listeners to be implemented in your language of choice. The event system has a retry semantic to allow for events to be replayed if a listener is ever offline as well as a set of REST resources to allow clients to read event history and delivery status. With the power of near real time event publishing many integrations can avoid the hassle of polling a resource for changes and instead react as events occur and let Mozu handle multi-threading concerns when multiple events occur at the same time. Open Source Applications As a way to remove costly barriers to development and innovation on Mozu, we ve made available several applications, resource kits, and jump start kits in github repos. Our goals is not to build a walled garden with a pay to play access model, the more we share with developers the better developers they will be on Mozu which benefits our clients and the entire ecosystem. Modern Developer Tooling Since developer productivity translates directly into client innovation we now how important developer tooling is for implementation teams and partners. Even though all Mozu hosted code assets will run in the Mozu cloud, we don t think all of the developer tooling should be forced to be in the cloud. Browser based code editors are not ideal and definitely impact developer productivity. Because of that, Mozu s developer tools are all locally running clients that allow developers to use the IDE of their choice and facilitate a tight feedback loop from between editing code, running a build, and viewing results in a dev environment. By allowing developers to work in tools they are comfortable with and supporting a short feedback loop Mozu can increase developer productivity and reduce implementation times. And because the Mozu platform automatically manages deployment of code assets into tenants and sandboxes the amount of deployment process burden placed on developers is greatly minimized. Mozu Technology 8

9 REGULAR UPDATES Enterprise retailers need a platform that will regularly and transparently be upgraded with new features as the market evolves Weekly Transparent Releases The Mozu engineering team has built a robust release train process that allows for weekly platform releases on a regular cadence. These releases are guaranteed to not break existing API contracts or existing implementations. The platform team has rigorous testing processes and pushes platform releases through multiple gates before it can every qualify as production ready. The final gate is a deployment to our production sandbox environment where all clients and partners to evaluate the changes prior to releasing to production sites. For larger clients, we also have the ability to hold platform releases (with constraints) for a limited time in order to avoid collisions with client launches. API Contract Preserves Customizations The backbone of our philosophy is a firm belief that clean, stable API contracts allow developers to move quickly and with assurances that their customizations will work across Mozu releases. Since initial launch over 2 years ago Mozu has had literally dozens of platform releases and has never once broken an API contract. This obsession with backwards compatibility and a firm belief that a boundary must exist between platform code and customizations is what allows the platform to innovate without requiring clients to be unnecessarily delayed in receiving those updates. Clients get the latest features without having to pay, run an upgrade, or re-implement. And in a time when the industry is changing dramatically this capability gives enterprises a distinct advantage by ensuring they can always have cutting edge technology and features available when they need it. Mozu Technology 9

Platform Beta Environment As the core Mozu platform evolves, both clients and Mozu benefit from early access to the advances that are under development.

10 Platform Beta Environment As the core Mozu platform evolves, both clients and Mozu benefit from early access to the advances that are under development. To facilitate this, Mozu has a fully functional beta environment which is available to partners and clients 24x7 with pre-released version of the Mozu platform installed. Our product team regularly engages clients to help them learn about and provide feedback on new features as they are deployed into the beta environment. In doing this we can ensure that features are of the highest quality before they are launched into production. Unlimited Sandboxes One big benefit to Saas solutions is the ability to quickly provision new environments using the provisioning and deployment automation provided by the platform. Mozu has a fully automated ability to create new tenants in a sandbox environment with support for cloning of all configuration, data, and application installations from a source tenant into a new tenant. And because creating a tenant puts no tenant specific configuration on an API or storefront server we can support incredible density in our sandbox environment. This allows us to offer unlimited sandboxes with no additional charge for clients or partners. Flexibility and low overhead in creating dev environments directly translates into client innovation and productivity. Mozu Technology 10

11 SCALING Enterprises need a platform that will be screaming fast at scale Mozu Internal Software Stack We have always been proud of hiring top engineering talent that brings a thoughtful, intelligent approach to software development there is no room for bringing religious platform biases into software architecture conversations. We believe in using the best tool for the problem being solved and also know that some platforms and technologies are better suited for solving certain kinds of problems. For that reason the internals of the platform are composed of a mixture of technologies: Java, F#, C#, C++, and NodeJs are the main stacks in use at Mozu. Because Mozu is based on Micro Services and we have a strong commitment to multiple platforms for our developer community we can seamlessly integrate these disparate stacks under the covers. Physical Architecture We took full advantage of having a distributed architecture by building a tremendous amount of flexibility into the physical architecture. Our goals were to provide fault isolation, dynamic scaling, and no hardware specialization. Mozu provides 3 levels of fault isolation through how the architecture is structured. There are 3 primary entities that make up the Mozu infrastructure: Pods, Scale Units, and Instances. A Pod is a physical facility with unique power and bandwidth feeds. A Pod can contain one to many Scale Units. A Scale Unit is a fully functioning set of Mozu infrastructure. It contains every unique server role required to run Mozu. Each Scale Unit has a complete set of clustered databases, search servers, event queues, micro service severs and application servers required to run Mozu. And each Scale Unit can contain one to many instances. A Mozu instance is a set of isolated compute that runs in a Scale Unit. Since all Mozu servers are stateless at the server level and do not persist any tenant specific state or configuration, the actual servers that are available to a Mozu instance is controlled by the routing of requests at the network level without any additional changes required to the servers in an instance. This provides tremendous flexibility in the use of Mozu resources and allows Mozu to shift workloads as necessary to satisfy bursts in demand. Every Mozu Instance is multi-tenant and can service one to many tenants. Some Scale Units can contain a single Mozu instance which hosts a single tenant, while our most extreme example is the Sandbox environment which contains tens of thousands of tenants in a handful of instances and a single Scale Unit. Mozu Technology 11

12 Instance Isolation Protecting tenant data and server resources from spilling over from one tenant to another is of critical importance to Mozu s success. Data isolation is guaranteed through standard practices which validate tenant context as soon as a request hit our outermost platform layer and is revalidated all the way through to the databases. This ensures that we will not have data spill across tenant boundaries. Additionally we have to protect server resources so that an issue with one tenant doesn t spill over into another tenant s resources. Mozu has varying levels of compute isolation and allows for tenant workloads to be shared or isolated depending on needs. These decisions can be made at runtime and our routing layer controls which resources are used to service each request. Since our servers are stateless, no additional provisioning or state management is required in advance in order to route a workload to new resources, it can happen dynamically on an as needed basis. We effectively protect tenants against CPU and memory constraints as well as thread starvation due to slow running dependent processes from other tenants. Dynamic Scaling One of the key principles that we strove to adhere to at Mozu was to maintain a strong abstraction between the platform specific state and the underlying infrastructure that supports it. While we take maximum advantage of the capabilities provided by the underlying OS that hosts Mozu sites and APIs in order to maximize performance and scalability, we didn t want to directly expose OS specific semantics to Mozu developers and users. The Mozu Core Abstraction layer is what provides that universal across every running instance of Mozu services. This layer gives us the flexibility to choose the underlying OS and versions without impacting existing implementations. Additionally this allows us to manage any server specific state within the Core layer - avoiding costly tenant specific configuration and state management during server provisioning. And we provision new servers at a pretty good clip. Our server provisioning automation can take bare metal gear to fully provisioned Mozu application server with the current platform components installed and taking traffic in under 15 minutes. By minimizing the unique server configurations for a scale unit, we have been able to simplify the provisioning infrastructure required to manage the environment. While Mozu servers have many different roles, the build is relatively standard across many roles. We continually evaluate the maximum role to workload distribution in order to provide the best service at the best cost. Mozu Technology 12

13 Distributed Cache Mozu s distributed cache was built specifically for a multi-tenant cloud environment where we knew data reader and writer processes would be distributed, cache data would be tenant specific, and known relationships between entities could be expressed programmatically for efficient cache management. The entire goal of the distributed cache is to allow server processes to leverage multiple levels of caches (in cost of access order) before having to retrieve data from the system of record. Systems of record (like a relational DB) have a tendency to be the first resources to bottleneck in a distributed environment. Inmemory caches are always preferred, and also come in many forms: page output caches, service output caches, single domain caches, and composite domain caches. All of Mozu s in-memory, distributed caches are backed by a MongoDB collection which tracks cache entry versions, expirations, and cache keys in addition to the actual cache data. For http output caches, those caches are stored as the on-the-wire output format to avoid the overhead of having to reserialize requested objects unnecessarily. This allows that cache code to be highly efficient in reading output cached objects from cache and writing them directly as a response. And because the caching infrastructure is intimately aware of Mozu request context headers, it can avoid unintentionally caching request specific state without platform developers having to remember every time they implement output caching on a Mozu endpoint. Dependencies between caches are expressed through programmatic tag assignment to cache entries. By forcing the cache contract between readers and writers to be a narrow set of tags we have decoupled writers from having to be aware of every single cache a reader implements. Eliminating unwanted dirty cache scenarios and freeing data writer processes be focused on a narrower set of caching concerns. Our preference is for cache readers to take as much of the burden as possible for understanding the structure and use of the caches. This allows readers to be as optimized as possible for their specific workloads and scenarios. Learn more about the Mozu platform technology and product development team. us at development@mozu.com or visit mozu.com/developers.

7 Things ISVs Must Know About Virtualization

7 Things ISVs Must Know About Virtualization July 2010 VIRTUALIZATION BENEFITS REPORT Table of Contents Executive Summary...1 Introduction...1 1. Applications just run!...2 2. Performance is excellent...2