I would like to understand from experience of others what are the best patterns to implement an e-commerce site using microservices?
This web site has different kinds of microservice patterns for you to go through. It also uses a fictitious e-commerce application as the example to explain some of the patterns. Perhaps you will find it helpful.
Related
When I am looking into approach's used for the development of API's, I came across multiple approaches like Code-First, API-First, Design-API-First.
I clearly understand Code-First approach how it is different from other two. But I am not able to get the exact difference between API-First and Design-First approach.
Summary from links:
API First:
API's are considered as first class citizens by the organization.
You design each of your APIs around a contract written in an API
description language like Open API for consistency, reusability, and broad
interoperability.
Design-API-First:
Describing every API design in an iterative way that both humans and computers can understand before you write any code.
API design-first is about the process of creating the API itself.
In design API first approach there will be lot of collaboration in designing of the API.
My understanding by far:
I feel 1 and 2 points of Design-API-First is saying same thing as API First because for example Open API specification is understood by both humans and computers. Is there anything more to it?
So, the only difference there will be collaboration added here by involving stakeholders, developers, customers etc?
So, when we use Design API First, we can say we are also using API-First?
References:
Probably I am able to get the exact context from the following links,
please use them and see if you can get the right understand of it and
address this question.
https://blog.stoplight.io/api-first-vs.-api-design-first-a-comprehensive-guide
https://blog.axway.com/product-insights/amplify-platform/application-integration/api-first-design-api-first
https://www.ecosmob.com/design-first-or-api-first-where-does-future-lies/
TLDR: I have been googling and finding opinions and blog posts but looking for some established (if any) Best Practices for Rest API Healthcheck development.
I work in prod support and I'm attempting to gather resources to make thing easier for our product teams when we introduce the idea "We are going to require endpoint healthchecks, here are our best practice guidelines and we based them on ........" I want them to be resources we can site (books or posts) and something respectable from larger organizations. We are working on building out more mature detection for our API services. Appreciate the help.
I will soon make a mobile application. For the front-end I will use React native and for the back-end I want to make an API but I don't know which technology to use, Django REST API, express js?
My problem is with regard to the videos to store, which technology is going to be the most suitable for storing them?
So, what technology would you use to create an API that can store videos properly and that will be called by react native?
There is no simple answer to a question like this. It all depends on your expectations, experience, resources, time, etc. It is also a very subjective question because most developers have their own preferences about these solutions. The truth is that you can build a solution in A LOT of different ways. Besides the JS frameworks you suggest, popular choices are .NET, PHP, C#, Ruby, Java and Python... and much more!
Besides the backend / API, you will also need a server for hosting your API and maybe another type of server for storage.
If you want to build everything yourself, take a look at the services provided by AWS, Azure or DigitalOcean. If you have limited experience building backends and want to save time, take a look at Google Firebase or Heroku.
The last two are plug-and-play solutions for expecially mobile apps like the one you are describing.
Check it all out and make your own opinion!
Good luck with your project! :-)
We are developing a LOB application using Silverlight and several team members are advocating the use of the canonical design pattern instead of creating simple WCF services. As the lead, I’m trying to balance best practices with an incredibly tight time line.
Here are the reasons I do NOT think Canonical is a good approach for our project.
We have no immediate (<5 years) requirement to expose any internal services to the enterprise.
Time required for governance. (Developing adapters with data transformation logic, developing XSDs, and developing contracts [fault, data, and operation]).
No need to expose a different data contracts than what exists in the data layer
It doesn’t appear that we can easily use ‘self tracking entities’ with the Canonical approach.
Here are some reasons I’m considering using Canonical approach.
We can use the XSD schemas for data type and length validation.
We will be prepared to allow consumption of our services to the enterprise, whether it’s 5 years or 1 year.
We can feel good that we’re implementing best practices. :)
So, is it advisable to follow the Canonical approach with a Silverlight application? It does not seem that the benefits Canonical provide out weigh the additional work. …or perhaps I’m wrong and it’s not additional work.
I think you should definitely go with WCF RIA services. It's extensible in every point possible, it's fast to develop, it's accessible as regular WCF services, it also has plenty different available end point types, and generally very mature. And implements best practices, and validation process is fully customizable. It really is a no brainer, if you have some additional questions about it shoot away, i'll gladly answer them:)
I was looking to get a prioritized list of things to look for while doing web site testing. There are things we could do to improve the performance of a site and there are things which affects the performance. Is there a guide for developer and testers to follow strictly which will deliver the best website experience?
Related:
What should a developer know before building a public web site?
For starters, Yahoo has a great list # Best Practices for Speeding Up Your Web Site.
For security there is OWASP Top Ten.
That your website works as expected on all major web browsers
The guys from Yahoo! have an excellent Developer's Network. Specifically you can look at their Guide to Exceptional Performance.
I would definitely recommend that you follow their suggestion to download Yslow for Firebug and use that to gauge your site's performance up front and then use its grading system as a way to improve performance.
Keep in mind that these are general rules of thumb and sometimes it is simply not possible to follow all of their best recommendations for improving performance.
Some security problems: Looking if Cross-Site-Scripting or Cross-Request-Forgery-attacks are possible. Can pages be accessed without login, if you know the URL?