The document provides an overview of the Salesforce1 Platform APIs, including the REST API, SOAP API, Chatter REST API, Analytics API, Streaming API, Custom APIs, Bulk API, Metadata API, and Tooling API. It describes the functionality, authentication methods, data formats, and synchronous/asynchronous capabilities of each API. Links are provided to documentation for further information on using the various Salesforce APIs.
Talk about Salesforce REST API: how to perform query, search or single-record CRUD operations; how to retrieve versions, list of custom object and object metadata and field metadata and presentation of demo page performing these requests
The document defines key terms related to the Anypoint Platform for APIs. It describes features like the analytics dashboard, API administration page, API creator role, API console, API designer, API portals, API version details page, API version owner role, developer portal, organization administration page, permissions, policies, roles, SLA tiers, and more. It provides concise explanations of each term and how they relate to developing and managing APIs within the Anypoint Platform.
This document provides an overview and user guide for the Anypoint Platform for APIs. It describes how to create an API in the platform, design the API, build it using RAML and APIkit, set the API URL, proxy the API, deploy it to CloudHub or on-premises, access APIs behind a firewall, manage APIs, create API notebooks, browse APIs in a developer portal, view API analytics, and use the analytics event API. The references section includes links to the Anypoint Platform for APIs documentation.
Anypoint Platform enables customers to be successful at all stages of integration from point-to-point to service orchestration to API management. The latest release brings together MuleSoft's leading application integration with powerful data integration capabilities, including integrated batch processing capabilities to move millions of records between applications quickly and reliably. It also includes Anypoint Templates for Salesforce to accelerate common integration use cases and increased productivity for data integration with enhanced features in Anypoint Studio.
MULE ESB provides an API layer that offers a decoupled interface for interacting with applications in a common, language-agnostic way. Common uses of an API layer include connecting to legacy applications that lack REST APIs or publishing APIs for partners to communicate with systems through a well-defined interface. The Anypoint Platform enables API-led connectivity by helping users build, design, and manage APIs from a single platform to expose enterprise data and applications in a secure and controlled way.
MuleSoft provides integration solutions for connecting Salesforce to other enterprise applications and CRM systems. This includes tools for consolidating, synchronizing and migrating CRM data between multiple instances. The Salesforce connector enables connecting Salesforce to ERP, analytics, billing and other applications through APIs. It supports over 57 operations across APIs like SOAP, Bulk REST, and Metadata. MuleSoft also offers a Salesforce Analytics Cloud connector to upload external data to the Analytics Cloud.
MuleSoft's Anypoint Platform allows developers to quickly connect applications and data from on-premise or cloud environments. It provides tools like Anypoint Studio for building integrations, Anypoint API Designer for designing REST APIs, Anypoint API Manager for managing APIs, and a library of pre-built connectors. It also includes MUnit for testing Mule applications and integrations. The platform aims to provide the fastest path to connectivity through an intuitive user experience and wide range of integration capabilities.
The document provides an overview of the Salesforce1 Platform APIs, including the REST API, SOAP API, Chatter REST API, Analytics API, Streaming API, Custom APIs, Bulk API, Metadata API, and Tooling API. It describes the functionality, authentication methods, data formats, and synchronous/asynchronous capabilities of each API. Links are provided to documentation for further information on using the various Salesforce APIs.
Talk about Salesforce REST API: how to perform query, search or single-record CRUD operations; how to retrieve versions, list of custom object and object metadata and field metadata and presentation of demo page performing these requests
The document defines key terms related to the Anypoint Platform for APIs. It describes features like the analytics dashboard, API administration page, API creator role, API console, API designer, API portals, API version details page, API version owner role, developer portal, organization administration page, permissions, policies, roles, SLA tiers, and more. It provides concise explanations of each term and how they relate to developing and managing APIs within the Anypoint Platform.
This document provides an overview and user guide for the Anypoint Platform for APIs. It describes how to create an API in the platform, design the API, build it using RAML and APIkit, set the API URL, proxy the API, deploy it to CloudHub or on-premises, access APIs behind a firewall, manage APIs, create API notebooks, browse APIs in a developer portal, view API analytics, and use the analytics event API. The references section includes links to the Anypoint Platform for APIs documentation.
Anypoint Platform enables customers to be successful at all stages of integration from point-to-point to service orchestration to API management. The latest release brings together MuleSoft's leading application integration with powerful data integration capabilities, including integrated batch processing capabilities to move millions of records between applications quickly and reliably. It also includes Anypoint Templates for Salesforce to accelerate common integration use cases and increased productivity for data integration with enhanced features in Anypoint Studio.
MULE ESB provides an API layer that offers a decoupled interface for interacting with applications in a common, language-agnostic way. Common uses of an API layer include connecting to legacy applications that lack REST APIs or publishing APIs for partners to communicate with systems through a well-defined interface. The Anypoint Platform enables API-led connectivity by helping users build, design, and manage APIs from a single platform to expose enterprise data and applications in a secure and controlled way.
MuleSoft provides integration solutions for connecting Salesforce to other enterprise applications and CRM systems. This includes tools for consolidating, synchronizing and migrating CRM data between multiple instances. The Salesforce connector enables connecting Salesforce to ERP, analytics, billing and other applications through APIs. It supports over 57 operations across APIs like SOAP, Bulk REST, and Metadata. MuleSoft also offers a Salesforce Analytics Cloud connector to upload external data to the Analytics Cloud.
MuleSoft's Anypoint Platform allows developers to quickly connect applications and data from on-premise or cloud environments. It provides tools like Anypoint Studio for building integrations, Anypoint API Designer for designing REST APIs, Anypoint API Manager for managing APIs, and a library of pre-built connectors. It also includes MUnit for testing Mule applications and integrations. The platform aims to provide the fastest path to connectivity through an intuitive user experience and wide range of integration capabilities.
Anypoint Platform for APIs allows users to build, manage, and share APIs through a single platform. It enables rapid development of new APIs and management of existing APIs. The platform includes components like the API Gateway and API Manager to design interfaces, apply policies, and provide analytics. The API Manager in particular allows users to proxy existing services, enforce policies, collect analytics, and deliver API portals to share APIs.
Anypoint Platform is a unified hybrid integration platform built on Mule runtime that offers tools to design, build, and manage APIs, applications, and products. It solves challenging connectivity problems across SOA, SaaS, and APIs through API-led connectivity. Key components include Mule runtime, Design Center, Management Center, Anypoint Connectors, Anypoint Exchange, and Runtime Services.
MULE ESB provides an API layer that offers a decoupled interface for interacting with applications in a common, language-agnostic way. An API layer is commonly used to connect to legacy applications that lack REST APIs or to publish partner-facing APIs. The Anypoint Platform enables API-led connectivity by helping users build, manage, and secure APIs from a single platform. It includes an API gateway for connecting to backends, an API manager for user management and monitoring, an API contract manager for access control, and an API policy manager for security policies.
RAML API Designer is a web-based graphical tool for designing, documenting, and testing APIs. It allows users to define APIs using the RAML specification, test API designs without writing code using an interactive console and mocking service, and share API designs and best practices.
This document discusses how to apply a rate limiting policy based on service level agreements (SLAs) to an API using MuleSoft API Gateway. It involves first creating SLAs with different rate limits. Then applications are associated with an SLA and requests are approved or require approval based on the SLA. The rate limiting policy is applied and uses the application client ID and secret to enforce the rate limits defined in the SLA. Tests are run to validate that requests for each application adhere to the limits of its assigned SLA tier.
CloudHub provides a variety of tools to architect your integrations and APIs so that they are maintainable, secure, and scalable. This guide covers the basic network architecture, DNS, and firewall rules.
The document discusses the features and capabilities of the Mule runtime engine of Anypoint Platform. It provides an enterprise service bus architecture that combines application and data integration across systems with a path to other Anypoint Platform capabilities and API connectivity. Key features highlighted include reliability, performance, scalability, security, graphical data integration, high availability, visibility, operational control, connectivity, security, and support.
Developing a CloudHub Application
The guide covers:
1) Specifying a Host address of 0.0.0.0 for CloudHub routing.
2) Providing an external HTTP/HTTPS port using ${http.port} or ${https.port} which is assigned by CloudHub.
3) Running applications locally by defining properties in mule-app.properties, including http.port or https.port.
The document discusses API layers in Mule and their uses. An API layer offers a decoupled interface for interacting with applications through a common language-agnostic way. Common uses of API layers include connecting to legacy systems that lack REST APIs and publishing APIs for partners to communicate with systems. The Anypoint Platform helps build, design, and manage APIs to expose enterprise data securely to various devices and apps. It includes an API gateway to connect to backends behind firewalls, an API manager to manage users and traffic, an API contract manager to issue keys and monitor compliance, and an API policy manager to apply security policies without downtime.
The document discusses MuleSoft's Mule platform for connecting software as a service (SaaS) applications. Some key points:
- Mule allows SaaS applications to connect to each other and to on-premises systems through its hybrid architecture.
- It provides unified connectivity across different integration technologies like APIs and SaaS applications, from simple to complex enterprise-grade connections.
- Mule's platform offers low friction development with reusable connectors and developer tools and can run integrations both in the cloud and on-premises.
The document outlines the roadmap for developing an Anypoint Connector, including setting up API access, creating a connector project, defining authentication, attributes, operations and data models, writing tests, documenting the connector, and packaging and releasing it. The process involves installing required tools, configuring authentication for the target API, modeling the API data and functionality, thoroughly testing the connector, documenting it using DevKit, and sharing the finished connector on the Anypoint Exchange if approved by any third-party licenses.
This document describes several Google connectors that are provided by Anypoint Platform from MuleSoft. It lists connectors for Google Prediction, Tasks, Contacts, Calendar, and Spreadsheets. Each connector allows integration between the respective Google service and third party applications by providing access to the Google APIs. The connectors allow applications to import, export, sync and modify data in Google services. This enables automation and extension of processes across different enterprise systems and departments.
This document provides information on various connectors available through the MuleSoft Anypoint Connectors. It lists 10 connectors: ActiveMQ, Cassandra DB, Database, Amazon S3, Amazon SQS, AMQP, Postgres, MySQL, Microsoft SQL Server, and Oracle Siebel. For each connector, it provides a brief 1-2 sentence description of the integration functionality and technologies supported. The connectors allow connecting applications, data, and devices to cloud and on-premises systems through APIs for various databases, messaging systems, storage services, and CRM platforms.
Mulesoft provides integration solutions tailored for mobile applications. Its Anypoint Platform for Mobile enables fast, easy development of mobile apps with API-led connectivity to backend systems and data sources. This allows for rapid development and change of mobile apps while providing enterprise-grade governance and control over data access. The platform also allows for connecting mobile apps to various data sources, rapid development and change of APIs, and self-service access to backend data through data gateways.
The document discusses MuleSoft's CloudHub platform, including:
1. CloudHub allows integration of SaaS, cloud, and enterprise applications in real-time and is built on Mule, the most widely used integration platform.
2. Advantages of CloudHub include availability, scalability, security, and zero downtime updates.
3. The CloudHub architecture provides deployment of applications from Anypoint Studio to CloudHub sites and management of applications and servers.
There are several ways to deploy Mule applications:
- Deploy to the Studio embedded test server for local testing.
- Export the application to a zip file and deploy it on an enterprise Mule server for production.
- Deploy to the Anypoint Platform for cloud-based deployment and management through Runtime Manager.
MuleSoft's Stripe connector allows developers to integrate their MuleSoft applications with the Stripe API to perform payment-related functions like accepting payments, creating invoices and customers. The document provides steps for setting up a Stripe developer account, configuring the Stripe API key, and using the Stripe connector in a Mule flow to create a customer and coupon in Stripe. Sample Mule flows are demonstrated to showcase how to trigger customer and coupon creation via HTTP requests.
Asynchronous Apex Salesforce World Tour Paris 2015Samuel De Rycke
The document discusses asynchronous Apex processing in Salesforce, including batch Apex, future methods, queueable Apex, scheduled Apex, and continuations. It describes when each would be used and how they allow processing to continue asynchronously rather than blocking the current transaction. It also provides examples of how to implement each type of asynchronous processing and notes some limitations, such as concurrent jobs limits and parameter passing restrictions.
Spring '16 release belgium salesforce user group samuel de ryckeSamuel De Rycke
The document summarizes the Spring '16 release from Salesforce including new features like:
- Global Actions/Docked Composer for keeping tasks visible while navigating
- Salesforce Field Service for work orders and hierarchical assets
- Authenticator app for two-factor authentication
- Salesforce1 offline capabilities for limited offline use
- Health Check security dashboard for reviewing org settings
It also provides next steps for learning more through Trailhead, release notes, communities, and YouTube and release timelines.
Getting Certified - proven tips for success (French Touch Dreamin)Samuel De Rycke
New to Salesforce certifications or haven’t been able to keep up with the growth of the different certifications out there? You’ll get an overview of all certifications with preparation recommendations and an overview of the best resources to guide you on your way. Presentation based on my own experience in becoming 12x Salesforce Certified and mentoring others going through the same journey.
Presented at French Touch Dreaming, Paris, November 17th, 2016. Using the Salesforce Dreamforce template.
Integration with the Salesforce App Cloud - Amsterdam 2016Samuel De Rycke
The document discusses integration with the Salesforce App Cloud. It provides an overview of integration, describing Salesforce's APIs, development toolkits, and standards that enable integration. These include the Partner API, Enterprise API, Bulk API, REST API, and Streaming API. It also discusses middleware like Dell Boomi, which provides an integration platform as a service (iPaaS) that allows "point and click" integration using extract, transform, load capabilities. The presentation includes a demo of integrating with Salesforce using Dell Boomi's APIs and user interface for bulk data loading.
Anypoint Platform for APIs allows users to build, manage, and share APIs through a single platform. It enables rapid development of new APIs and management of existing APIs. The platform includes components like the API Gateway and API Manager to design interfaces, apply policies, and provide analytics. The API Manager in particular allows users to proxy existing services, enforce policies, collect analytics, and deliver API portals to share APIs.
Anypoint Platform is a unified hybrid integration platform built on Mule runtime that offers tools to design, build, and manage APIs, applications, and products. It solves challenging connectivity problems across SOA, SaaS, and APIs through API-led connectivity. Key components include Mule runtime, Design Center, Management Center, Anypoint Connectors, Anypoint Exchange, and Runtime Services.
MULE ESB provides an API layer that offers a decoupled interface for interacting with applications in a common, language-agnostic way. An API layer is commonly used to connect to legacy applications that lack REST APIs or to publish partner-facing APIs. The Anypoint Platform enables API-led connectivity by helping users build, manage, and secure APIs from a single platform. It includes an API gateway for connecting to backends, an API manager for user management and monitoring, an API contract manager for access control, and an API policy manager for security policies.
RAML API Designer is a web-based graphical tool for designing, documenting, and testing APIs. It allows users to define APIs using the RAML specification, test API designs without writing code using an interactive console and mocking service, and share API designs and best practices.
This document discusses how to apply a rate limiting policy based on service level agreements (SLAs) to an API using MuleSoft API Gateway. It involves first creating SLAs with different rate limits. Then applications are associated with an SLA and requests are approved or require approval based on the SLA. The rate limiting policy is applied and uses the application client ID and secret to enforce the rate limits defined in the SLA. Tests are run to validate that requests for each application adhere to the limits of its assigned SLA tier.
CloudHub provides a variety of tools to architect your integrations and APIs so that they are maintainable, secure, and scalable. This guide covers the basic network architecture, DNS, and firewall rules.
The document discusses the features and capabilities of the Mule runtime engine of Anypoint Platform. It provides an enterprise service bus architecture that combines application and data integration across systems with a path to other Anypoint Platform capabilities and API connectivity. Key features highlighted include reliability, performance, scalability, security, graphical data integration, high availability, visibility, operational control, connectivity, security, and support.
Developing a CloudHub Application
The guide covers:
1) Specifying a Host address of 0.0.0.0 for CloudHub routing.
2) Providing an external HTTP/HTTPS port using ${http.port} or ${https.port} which is assigned by CloudHub.
3) Running applications locally by defining properties in mule-app.properties, including http.port or https.port.
The document discusses API layers in Mule and their uses. An API layer offers a decoupled interface for interacting with applications through a common language-agnostic way. Common uses of API layers include connecting to legacy systems that lack REST APIs and publishing APIs for partners to communicate with systems. The Anypoint Platform helps build, design, and manage APIs to expose enterprise data securely to various devices and apps. It includes an API gateway to connect to backends behind firewalls, an API manager to manage users and traffic, an API contract manager to issue keys and monitor compliance, and an API policy manager to apply security policies without downtime.
The document discusses MuleSoft's Mule platform for connecting software as a service (SaaS) applications. Some key points:
- Mule allows SaaS applications to connect to each other and to on-premises systems through its hybrid architecture.
- It provides unified connectivity across different integration technologies like APIs and SaaS applications, from simple to complex enterprise-grade connections.
- Mule's platform offers low friction development with reusable connectors and developer tools and can run integrations both in the cloud and on-premises.
The document outlines the roadmap for developing an Anypoint Connector, including setting up API access, creating a connector project, defining authentication, attributes, operations and data models, writing tests, documenting the connector, and packaging and releasing it. The process involves installing required tools, configuring authentication for the target API, modeling the API data and functionality, thoroughly testing the connector, documenting it using DevKit, and sharing the finished connector on the Anypoint Exchange if approved by any third-party licenses.
This document describes several Google connectors that are provided by Anypoint Platform from MuleSoft. It lists connectors for Google Prediction, Tasks, Contacts, Calendar, and Spreadsheets. Each connector allows integration between the respective Google service and third party applications by providing access to the Google APIs. The connectors allow applications to import, export, sync and modify data in Google services. This enables automation and extension of processes across different enterprise systems and departments.
This document provides information on various connectors available through the MuleSoft Anypoint Connectors. It lists 10 connectors: ActiveMQ, Cassandra DB, Database, Amazon S3, Amazon SQS, AMQP, Postgres, MySQL, Microsoft SQL Server, and Oracle Siebel. For each connector, it provides a brief 1-2 sentence description of the integration functionality and technologies supported. The connectors allow connecting applications, data, and devices to cloud and on-premises systems through APIs for various databases, messaging systems, storage services, and CRM platforms.
Mulesoft provides integration solutions tailored for mobile applications. Its Anypoint Platform for Mobile enables fast, easy development of mobile apps with API-led connectivity to backend systems and data sources. This allows for rapid development and change of mobile apps while providing enterprise-grade governance and control over data access. The platform also allows for connecting mobile apps to various data sources, rapid development and change of APIs, and self-service access to backend data through data gateways.
The document discusses MuleSoft's CloudHub platform, including:
1. CloudHub allows integration of SaaS, cloud, and enterprise applications in real-time and is built on Mule, the most widely used integration platform.
2. Advantages of CloudHub include availability, scalability, security, and zero downtime updates.
3. The CloudHub architecture provides deployment of applications from Anypoint Studio to CloudHub sites and management of applications and servers.
There are several ways to deploy Mule applications:
- Deploy to the Studio embedded test server for local testing.
- Export the application to a zip file and deploy it on an enterprise Mule server for production.
- Deploy to the Anypoint Platform for cloud-based deployment and management through Runtime Manager.
MuleSoft's Stripe connector allows developers to integrate their MuleSoft applications with the Stripe API to perform payment-related functions like accepting payments, creating invoices and customers. The document provides steps for setting up a Stripe developer account, configuring the Stripe API key, and using the Stripe connector in a Mule flow to create a customer and coupon in Stripe. Sample Mule flows are demonstrated to showcase how to trigger customer and coupon creation via HTTP requests.
Asynchronous Apex Salesforce World Tour Paris 2015Samuel De Rycke
The document discusses asynchronous Apex processing in Salesforce, including batch Apex, future methods, queueable Apex, scheduled Apex, and continuations. It describes when each would be used and how they allow processing to continue asynchronously rather than blocking the current transaction. It also provides examples of how to implement each type of asynchronous processing and notes some limitations, such as concurrent jobs limits and parameter passing restrictions.
Spring '16 release belgium salesforce user group samuel de ryckeSamuel De Rycke
The document summarizes the Spring '16 release from Salesforce including new features like:
- Global Actions/Docked Composer for keeping tasks visible while navigating
- Salesforce Field Service for work orders and hierarchical assets
- Authenticator app for two-factor authentication
- Salesforce1 offline capabilities for limited offline use
- Health Check security dashboard for reviewing org settings
It also provides next steps for learning more through Trailhead, release notes, communities, and YouTube and release timelines.
Getting Certified - proven tips for success (French Touch Dreamin)Samuel De Rycke
New to Salesforce certifications or haven’t been able to keep up with the growth of the different certifications out there? You’ll get an overview of all certifications with preparation recommendations and an overview of the best resources to guide you on your way. Presentation based on my own experience in becoming 12x Salesforce Certified and mentoring others going through the same journey.
Presented at French Touch Dreaming, Paris, November 17th, 2016. Using the Salesforce Dreamforce template.
Integration with the Salesforce App Cloud - Amsterdam 2016Samuel De Rycke
The document discusses integration with the Salesforce App Cloud. It provides an overview of integration, describing Salesforce's APIs, development toolkits, and standards that enable integration. These include the Partner API, Enterprise API, Bulk API, REST API, and Streaming API. It also discusses middleware like Dell Boomi, which provides an integration platform as a service (iPaaS) that allows "point and click" integration using extract, transform, load capabilities. The presentation includes a demo of integrating with Salesforce using Dell Boomi's APIs and user interface for bulk data loading.
Lightning Chess at the Sri Sanka Salesforce Developer GroupSamuel De Rycke
Introduction to architecting applications with the Salesforce Lightning Component Framework in a fun way, using a multiplayer chess game and example application.
Salesforce API Series: Integrating Applications with Force.com WebinarSalesforce Developers
Force.com APIs allow you to easily integrate back-office applications with Force.com while leveraging existing platform choices for systems like ERP, Financials and other custom applications. This webinar, the first in a series covering all Salesforce APIs, focuses on the SOAP and REST APIs, and will present asynchronous integration options, showing how they can be used to access data in Force.com and connect other applications to Force.com. Future webinars will focus on the APIs specific to Service Cloud, Collaboration, Metadata and the Tooling API.
Watch this webinar to learn how to make basic API calls using Java, and implement inbound and outbound calls to and from Force.com.
Key Takeaways
Learn about the various API options available to you when integrating Force.com with other applications.
See how the basic SOAP and REST APIs work in an application.
Implement a commonly used pattern to integrate information from Force.com to an external system.
Intended Audience
Force.com developers or Integration developers and architects with a working understanding of Web Services.
This document discusses Meyn's implementation of a new parts manual system using Salesforce Lightning components and technologies. It summarizes Meyn's vision for a customer community, demonstrates the new Lightning parts manual, and outlines the high-level solution design including using Lightning components and Lightning Out to build custom components natively, and Lightning Connect to integrate SharePoint data in real-time. Some challenges discussed are Lightning's lack of support for interactive SVGs and standard PDF printing of SVGs. The presentation concludes by emphasizing customer enablement and success through the new system.
The document discusses company updates at ABSI, including the API economy and what makes ABSI unique. It focuses on operational excellence, quality delivery, and helping customers move applications flexibly to private or public clouds to reduce costs and support business goals. The document concludes with thanking customers, partners, and the ABSI team for their contributions.
Absi summmer BBQ Presentation on Going DigitalABSI_NV
A presentation by Doubi Ajami of ABSI from the annual summer BBQ event at Technopolis in Mechelen, The topics covered are the need to Go Digital and ABSI'a own digital transformation.
Slides from the presentation at the Salesforce Word Tour event in Amsterdam (April 14th 2016) about Custome Metadata Data Types, given in the Trailhead Zone
As more and more applications are adopting the API-first approach, it's important to understand that building and using APIs comes with its own set of security concerns, even though it abstracts away the issues caused at the presentation layer. Join us as we dive deeper into best practices for building secure API endpoints. We'll also discuss the importance of transport security and common pitfalls in SSL configurations.
The marketing technology landscape is at war. Can a single tool unite the kingdom, provide the personal attention your subjects are craving, and defeat the white walkers...er, your competitors?
Have you ever wanted to schedule an Apex operation to repeat every 10 minutes? To have one future call start another one? Is the 10 future call per context limit getting you down? Recent additions to the Apex language have opened the door to entirely new asynchronous design patterns. Join us to learn about the recent language changes, how they are used, and the kinds of design patterns they enable.
When executing something synchronously, you wait for it to finish before moving on to another task. Asynchronously, you can move on before it finishes. Future methods, Queueable Apex, and Batch Apex allow asynchronous execution in Apex. Future methods are best for long-running methods or callouts. Queueable Apex allows job chaining and passing complex types. Batch Apex is best for large data volumes processed in batches. Continuations allow asynchronous callouts from Visualforce pages.
Batchable, @future, and Queueable are interfaces in Apex that allow for asynchronous and batch processing.
Batchable is used for processing large numbers of records asynchronously in batches of up to 50 million records. It defines start(), execute(), and finish() methods and allows scheduling batch jobs to run at a specific time. However, there are limits such as only 5 concurrent batch jobs and no @future calls allowed within a batch.
@future allows for simple, frequent asynchronous processing of single records through static void methods but only supports primitive arguments. It has no concurrency limits but parameters are limited and jobs cannot be chained.
Queueable is used when Batchable and @future need to be combined, such
Governor limits in Salesforce enforce runtime limits on Apex code to ensure fair sharing of system resources among multiple tenants. The key governor limits include limits on the number of SOQL queries, records retrieved, and number of scripts executed. Governor limits are calculated based on the entry point for the Apex code, such as Apex triggers, web services, or anonymous blocks. Limits are shared across an organization and apply to all code executed within a synchronous transaction, while asynchronous code like future methods has separate limits. Developers must optimize code to avoid hitting governor limits, for example by bulkifying code, minimizing SOQL queries, and using future calls appropriately.
Building Content-Rich Java Apps in the Cloud with the Alfresco APIJeff Potts
This presentation, originally delivered at JavaOne on October 2, 2012, talks about why you should use Alfresco instead of rolling your own content repository and discusses the new public Alfresco API for writing content apps that persist content to Alfresco in the Cloud.
RESTful web APIs (build, document, manage)Cisco DevNet
- RESTful Web APIs are the fuel of the web. The class will cover building, documenting, and managing RESTful web APIs.
- There are different approaches to designing web APIs, from a basic design with no distinction between app and backend, to more advanced "API-centric" designs that move business logic and security to the API.
- Web APIs can be built using frameworks like Sails.js or platforms like APISpark. They also need to be documented, monitored, and managed over their lifecycle. Tools like Swagger, Runscope, and API management platforms can help with these tasks.
Steve Sfartz, VP Engineering of Restlet shares our experience in building a web API via DIY (Do It Yourself) approach or via PaaS approach (APISpark). Introduction to both open source Restlet Framework and public beta of APISpark.
Design & Deploy a data-driven Web API in 2 hoursRestlet
Learn how to use the ROA/D process along with UX and DDD to design a proper web API, then learn how APISpark platform (PaaS) compares to a DIY approaches.
Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. With a few clicks in the AWS Management Console, you can create an API that acts as a “front door” for applications to access data, business logic, or functionality from your back-end services, such as workloads running on Amazon Elastic Compute Cloud (Amazon EC2), code running on AWS Lambda, or any Web application.
Amazon API Gateway is a fully managed service that makes it easy for developers to create, deploy, secure and monitor APIs at any scale. In this session, you’ll find out how you can quickly declare an API interface and connect it to any public HTTP endpoint, existing web service running on Amazon Elastic Compute Cloud (Amazon EC2) or code running on AWS Lambda. Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management. Join us for this introductory session to Amazon API Gateway.
AWS Summit Barcelona 2015 - Introducing Amazon API GatewayVadim Zendejas
Amazon API Gateway was created to address challenges customers faced in managing and monitoring APIs. It allows users to host multiple API versions and stages, generate and distribute API keys to developers, and leverage SigV4 to authorize access. API Gateway provides features like throttling, caching, and SDK generation to help manage traffic and access to backend services. It offers a serverless way to deploy APIs without having to provision or manage servers.
Flink Forward San Francisco 2018: Dave Torok & Sameer Wadkar - "Embedding Fl...Flink Forward
This document discusses using Apache Flink to operationalize a streaming machine learning lifecycle. It describes Comcast's need to improve customer experiences through predictive analytics over streaming data. Flink is used to orchestrate feature engineering, model training/evaluation, and real-time predictions. Key aspects of the solution include a metadata-driven pipeline, automated deployments, consistent feature stores for training and prediction, and monitoring of multiple models. The document outlines the various components of the ML lifecycle and pipeline implemented on Flink and discusses next steps around UI/UX, continuous monitoring, and supporting multiple feature stores.
This document discusses RESTful microservices and best practices for designing REST APIs. It covers topics like why REST is important for API design, common REST principles, naming conventions, resource relationships, security, versioning, documentation, and management of REST APIs. It also provides examples of how various companies implement practices like filtering, searching, paging, and error handling in their REST APIs. Finally, it discusses how the WebSphere Liberty application server supports REST APIs through features like API discovery and collective APIs.
(Almost) All About Apps for SharePoint 2013Dragan Panjkov
This slide deck is presented on Microsoft TechNet Day 2012, organized in Bosnia and Herzegovina. Main goal of this presentation is to introduce new SharePoint Apps to end users, developers and administrators.
Developer’s Independence Day:Introducing the SharePoint App Modelbgerman
The document introduces the SharePoint app model, which modernizes SharePoint development. It discusses moving from the MS DOS application model to a more modern approach with app isolation, process isolation, and app-based permission schemes. It covers SharePoint hosted apps and provider hosted apps, and demonstrates examples of each. The document also discusses accessing SharePoint data through REST APIs and the client-side object model, and authentication approaches like OAuth.
This mid-level technical session will help you choose among the AWS services that can help you deploy and run your applications more easily. You will learn how to get an application running using AWS OpsWorks and AWS Elastic Beanstalk and how to use AWS CloudFormation templates to document, version control, and share your application configuration
Learn how to monitor and manage your serverless APIs in production. We show you how to set up Amazon CloudWatch alarms, interpret CloudWatch logs for Amazon API Gateway and AWS Lambda, and automate common maintenance and management tasks on your service.
API Description Languages: Which Is The Right One For Me? ProgrammableWeb
The document discusses and compares different API description languages (APIs), including RAML and Swagger. It provides an overview of each tool's features and capabilities. The document also shares the author's experiences using RAML and Swagger to describe sample APIs. While both APIs are useful for documentation, the author found RAML better suited for designing APIs first before coding, while Swagger integrates more tightly with code.
REST is a lightweight architecture for building client-server applications. It uses standard HTTP methods to allow requesting and modifying resource state representations. While SOAP and web services will continue to be used, REST is better suited for mobile and web applications. Organizations are realizing they cannot replace existing technologies and instead focus on integrating technologies to leverage their respective strengths. Exposing existing systems through a REST API gateway allows for coexistence while providing a clean interface. Security, caching, throttling and monitoring are important when managing REST APIs at an enterprise scale.
Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. It allows developers to manage multiple versions and stages of APIs, monitor access by third party developers, and handle traffic spikes without operational burden. API Gateway supports features like throttling, authorization, caching of responses, and SDK generation to make APIs easy to consume.
Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. It allows developers to manage multiple versions and stages of APIs, monitor access by third party developers, and handle traffic spikes without operational burden. API Gateway supports features like request throttling, authorization, caching, and SDK generation to help secure and scale APIs.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
What is Master Data Management by PiLog Groupaymanquadri279
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Atelier - Innover avec l’IA Générative et les graphes de connaissancesNeo4j
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
SMS API Integration in Saudi Arabia| Best SMS API ServiceYara Milbes
Discover the benefits and implementation of SMS API integration in the UAE and Middle East. This comprehensive guide covers the importance of SMS messaging APIs, the advantages of bulk SMS APIs, and real-world case studies. Learn how CEQUENS, a leader in communication solutions, can help your business enhance customer engagement and streamline operations with innovative CPaaS, reliable SMS APIs, and omnichannel solutions, including WhatsApp Business. Perfect for businesses seeking to optimize their communication strategies in the digital age.
Using Query Store in Azure PostgreSQL to Understand Query PerformanceGrant Fritchey
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
3. SOAP API
• SOAP/WSDL
• 2 Versions:
• Enterprise: Strongly typed, Org specific
• Partner: Dynamic, Requires datamodel inspection
• Extensive API, well suited for system integrations
• https://www.salesforce.com/us/developer/docs/api/
4. REST API
• Access data over REST
• XML or JSON
• Lightweight
• Best suited for browser or mobile applications
• https://www.salesforce.com/us/developer/docs/api_rest/
5. Custom APIs
• Apex code
• SOAP or REST
• XML, JSON or custom formats
• Synchronous
• Write your own API inApex
• https://developer.salesforce.com/page/Apex_Web_Services
6. Custom APIs – Use Case
• Challenge: External mobile application needs to store multiple records in multiple objects
in a transactional process.
• Issue: RESTApi handles insert and update calls in separate requests per record
• Solution: We wrote our own custom Apex REST endpoint to accept a custom datatype
which was wrapper around the salesforce sObjects. Now we could handle the transactional
process in Apex.
7. Chatter REST API
• REST
• XML or JSON
• Synchronous
• Abstracted data model
• Chatter specific API to access the social collaboration part of force.com
• http://www.salesforce.com/us/developer/docs/chatterapi/
8. BULK API
• REST
• XML or CSV
• Asynchronous
• Process >1.000.000 records
• https://www.salesforce.com/us/developer/docs/api_asynch/
9. Analytics API
• REST
• JSON
• Synchronous &Asynchronous
• Access the force.com reporting engine: configuration and data
• http://www.salesforce.com/us/developer/docs/api_analytics/index.htm
10. Streaming API
• JSON
• Asynchronous
• Near real-time
• Receive push notifications when records are created or updated
• http://www.salesforce.com/us/developer/docs/api_streaming/
11. Metadata API
• SOAP/WSDL
• Access the force.com configuration
• Deploy between orgs !
• http://www.salesforce.com/us/developer/docs/api_meta/
12. Tooling API
• SOAP or REST
• XML or JSON
• Exposes developer features
• http://www.salesforce.com/us/developer/docs/api_tooling/index.htm
Users, groups, composite feed posts, followers and files. Abstracted data model -> logical data model. API similar to those of Twitter or Facebook.
Optimized for manipulating large sets of data. Batchese are processed asynchronously. SETUP > Monitor > JOBS > Bulk Data Load Jobs
Implemented in the salesforce dataloader
Access to report data as configured in the report builder. Use report data in custom objects. Custom visualizations. Automate reporting tasks, Filter on the fly.