What is Model View Controller (MVC)?
The Model-View-Controller pattern is a powerful way to structure an application and provide clear separation of concerns between different components.
The Model-View-Controller pattern is a powerful way to structure an application and provide clear separation of concerns between different components.
I’m really excited to announce that I am writing a book on Lightning Web Component development for Packt Publishing.
A database is a crucial part of any software system, storing and managing the data that powers your applications.
In order to ensure the longevity, maintainability, and reliability of your database, it is essential to document it thoroughly.
Regular expressions, also known as RegEx, are a powerful tool that can be used to search, match, and manipulate strings in various programming languages.
In this blog post, we’ll explore some requirements that API developers need to consider when designing and building an API.
In this blog article, we covered what a JSONWeb Token (JWT) is, how to create a JWT, and how to verify a JWT.
No! Salesforce Lightning Components (Aura Components) are likely to live on for quite a few years. I do think that the Lightning Web Component will eventually lead to the Lightning Component falling out of use.
There is no requirement right now to completely rebuild Aura components because Aura and Lightning Web Components can work together. They are completely interoperable.
Master data management (MDM) is the process and tools that are used to reduce redundancy and conflicting information.
The API architecture is made up of four different layers: the Interaction Layer, Integrational Layer, Application Layer, and Information Management Layer (databases).
If an API isn’t documented, the chance of it being consumed by other developers is incredibly low. For a very long time, companies like Microsoft, Salesforce, and Apple were dominant players in technology. They were dominant players because they had a compelling product and great documentation.
An API First Approach implies that the API is a first class citizen. The API is developed with the goal of API consumption in mind. The API is our point of differentiation.
An API program is a plan that a company has developed to market, support and monetize a public API. There are thousands – maybe even tens of thousands of companies with public and open APIs.
REST and SOAP are different ways of transmitting data between two different systems via an API. REST is a set of architectural principles. SOAP is a protocol maintained by the World Wide Web Consortium.
A unified API is an abstraction that allows us to combine APIs for multiple providers – giving us one place to access all of their endpoints.
When building and maintaining APIs there are a lot of different terminology that you need to be aware of. This isn’t a complete list, but it’s enough to make you dangerous.
Enterprise Resource Planning (ERP) system implementations often fail. Most ERP implementations fail the first time around OR go dramatically over budget or take longer than expected.
When connecting to the Salesforce SOAP API, there’s two different WSDL options: the Enterprise WSDL and the Partner WSDL.
Apex classes and methods can be exposed to external applications as REST based endpoints.
This means that there’s a very easy way to have an external application make a direct call into Salesforce to do a specific action.
Handling no results in a collection endpoint and at a singular resource can be a bit of a tricky situation.