Amazon S3 is a cloud-based object storage service from Amazon Web Services. It's key features are storage management and monitoring, access management and security, data querying, and data transfer.
N/A
Epicor Eclipse
Score 4.4 out of 10
N/A
Epicor Eclipse is an end-to-end business system for wholesale distributors, as well as electrical, HVAC, plumbing and PVF businesses. Eclipse simplifies complex distribution processes found in today’s dynamic supply chains.
N/A
Microsoft Azure
Score 8.4 out of 10
N/A
Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
Pricing
Amazon S3 (Simple Storage Service)
Epicor Eclipse
Microsoft Azure
Editions & Modules
No answers on this topic
No answers on this topic
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
Offerings
Pricing Offerings
Amazon S3
Epicor Eclipse
Microsoft Azure
Free Trial
No
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
More Pricing Information
Community Pulse
Amazon S3 (Simple Storage Service)
Epicor Eclipse
Microsoft Azure
Considered Multiple Products
Amazon S3
Verified User
C-Level Executive
Chose Amazon S3 (Simple Storage Service)
Amazon S3 is more cost-effective then what Microsoft Azure offers.
When we were implementation the solution of our issue then we find Azure and Google Cloud Storage platforms but we were unable to find the proper documentation for the platform as compared to S3, So we moved to S3 and discarded the other options. Cost wise there are only some …
S3 provides an on-demand usage model for storage. You only pay for what you use. Nutanix is an on-premises solution and does not allow for usage-based pricing. Azure was less integrated with our current AWS workloads which helped drive our decision to use s3 with the Amazon …
Amazon S3 comes with all other services of AWS, all other services are very quick and secure with S3 storage, which is the best option for any application. Again, compared to other services like Azure or GCP, AWS provides more configuration and functions to host multi nature …
Some obvious ones are Google storage services like Drive, and their whole arsenal of services. Another could be the Office line where SharePoint and other programs can be used synchronously. I have seen other people use Windows Azure for storage needs similar to ours. We chose …
Amazon has had years of development in building their cloud solution. A few other vendors are playing catch up but that's always the case when you have the key to success. The saying goes " if you built it, they will come". :)
Azure provides an environment that while at time is more pricey, the tight integration with our existing Microsoft-based infrastructure makes it difficult to beat.
AWS is competitor and it's leading in cloud space with his wide sprawl of offerings and services. AWS is a ocean once you login you get everything on one console. AWS leads this space with all his offerings and capabilities. But Azure is not behind, it is competing and is …
Amazon S3 is a great service to safely backup your data where redundancy is guaranteed and the cost is fair. We use Amazon S3 for data that we backup and hope we never need to access but in the case of a catastrophic or even small slip of the finger with the delete command we know our data and our client's data is safely backed up by Amazon S3. Transferring data into Amazon S3 is free but transferring data out has an associated, albeit low, cost per GB. This needs to be kept in mind if you plan on transferring out a lot of data frequently. There may be other cost effective options although Amazon S3 prices are really low per GB. Transferring 150TB would cost approximately $50 per month.
Eclipse is well suited for quick order entry where the source is a formal purchase order document or a phone call with a known customer. In these scenarios the order entry process is quick, and order processing is smooth even if the customer has a lot of "special" requests like shipping part today and holding the rest or shipping some of the order to other addresses. Eclipse also works well if you have a good database of products, especially in searching for products where only partial information is known or finding existing orders where all you know for sure is the customer. It is not particularly well suited for Point of Sale where a walk-in customer who doesn't have an account wants products for which part numbers are not known, due to the requirements to release an order for a customer with no credit.
Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.
Fantastic developer API, including AWS command line and library utilities.
Strong integration with the AWS ecosystem, especially with regards to access permissions.
It's astoundingly stable- you can trust it'll stay online and available for anywhere in the world.
Its static website hosting feature is a hidden gem-- it provides perhaps the cheapest, most stable, most high-performing static web hosting available in PaaS.
Sales Order tracking, even returns are strengths of Epicor Eclipse. It can be set up to match returns to previous orders so that the correct credits are applied. It is capable of setting up contract pricing as well as matrix level pricing according to sales velocity or individual customer buyer programs.
Purchasing can be set up to work by full line buys or short buys while still maintaining a balanced inventory level of vendor line product.
Vendor Invoices and purchase orders are easily matched up for payment and the diverse reporting features are able to provide multi-faceted views of Product Sales, Items with No Sales, or Sales or Purchasing trends, just to name a few.
It is also tracking warehouse operation in both RF and non-RF environments, or a combination of the two.
Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.
Web console can be very confusing and challenging to use, especially for new users
Bucket policies are very flexible, but the composability of the security rules can be very confusing to get right, often leading to security rules in use on buckets other than what you believe they are
The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
The documentation needs to be improved, and some advanced configuration options require research and experimentation.
Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.
I use it every day and can't see a reason why I would stop unless I started a new job. If I were to leave my present position, the new job would be much more attractive if they were Eclipse users.
Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.
It is tricky to get it all set up correctly with policies and getting the IAM settings right. There is also a lot of lifecycle config you can do in terms of moving data to cold/glacier storage. It is also not to be confused with being a OneDrive or SharePoint replacement, they each have their own place in our environment, and S3 is used more by the IT team and accessed by our PHP applications. It is not necessarily used by an average everyday user for storing their pictures or documents, etc.
This is very easy to use for someone that hasn't ever used the system before. Despite any preconceived notions about how a system should function they can learn this and become efficient with really not a lot of effort. I have used many systems and this is probably one of the easiest I have ever had to learn to navigate and use.
As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.
I haven't experienced any outages in the two years I have been using the system. It is always available as long as the computer is up. The only time I have seen it not be available was on occasions where we lost internet, or power and then we lost access to everything, not just Epicor Eclipse.
Everything in this system moves fairly quickly, that may be in part because we are a small company with only 21 users on the system at a time, or it may just be a the way the Epicor Eclipse works for any size company with any number of users. I can only speak for what I know and say that it is fast for our purposes.
AWS has always been quick to resolve any support ticket raised. S3 is no exception. We have only ever used it once to get a clarification regarding the costs involved when data is transferred between S3 and other AWS services or the public internet. We got a response from AWS support team within a day.
The tier 1 support is trying, and sometimes they are successful. Sometimes they aren't. This topic isn't as black and white as the questions might suggest. Currently their Tier 1 support team is over seas, all items automatically go to Tier 1 and then when they can't help they either escalate it or tell me they need to check with someone else and they will get back to me. If they escalate me to Tier 2, then the issue comes back to the States and the support is usually at a higher knowledge/experience level and it can get resolved fairly quickly. If they don't escalate, then it might take weeks and multiple follow ups on my part before I either get a satisfactory resolution or finally get escalated.
We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!
The training classes that I have attended have been top notch. The presenters are extremely knowledgeable on their subject matter, including real-world application of the system. They aren't just software techs training end users, they seem to be end users that have become experts in the over functionality and capabilities of the system.
The on-line training is very good, and it is taught by the same people that do the live in-person training sessions. The difficult part of it is, asking questions about your specific company's nuances or special circumstances. I don't remember if you can access the on-line training sessions after you have taken them for reminders purposes, but if so that is a great asset.
I don't really know about the implementation, it was back in 1998 and I didn't start here until 2016. By the time I started here they had been running it for a number of years and most of the people that were here when it was implemented are no longer here, and the ones that are don't really have much to say about how the implementation went either bad or good.
As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
Overall, we found that Amazon S3 provided a lot of backend features Google Cloud Storage (GCS) simply couldn't compare to. GCS was way more expensive and really did not live up to it. In terms of setup, Google Cloud Storage may have Amazon S3 beat, however, as it is more of a pseudo advanced version of Google Drive, that was not a hard feat for it to achieve. Overall, evaluating GCS, in comparison to S3, was an utter disappointment.
Most of my experience has been with Epicor's Prophet 21. For most distribution verticals, Prophet 21 is the only way to go. The comparison I've drawn is this: Prophet 21 is like a ferrari. Epicor Eclipse is like a reliable donkey. Both get you from point A to point B but Prophet 21 is going to get you there much quicker and with the kind of insight into your business that will help you thrive.
As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.
I don't really know about the scalability. It's the same as it was when I started, I do know that you can buy more user licenses, but I think they come in packs of 5, which can be a problem if you only need 1 and will never use the other 4. But, again I'm not sure on that.
It practically eliminated some real heavy storage servers from our premises and reduced maintenance cost.
The excellent durability and reliability make sure the return of money you invested in.
If the objects which are not active or stale, one needs to remove them. Those objects keep adding cost to each billing cycle. If you are handling a really big infrastructure, sometimes this creates quite a huge bill for preserving un-necessary objects/documents.
One of the main positive ROI impacts has been the constant upgrading and adding of new features to keep the software user friendly, relative, and robust.
Our credit manager has said it has made their job easier with daily reports to catch pricing discrepancies and straighten out before they go to invoice makes us look better.
With the addition of sale analytics it has given our sales force tools and new approaches to our customer base which has raised profitability.
For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.
