Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Would you trust Jelastic if you were to use it for a SaaS application targeted at Enterprise customers?
I'm using it right now for its ease of use in creating a stack for a Java applcation. But it almost feels too easy.
What are you thoughts?
Jelastic is a universal product, designed and developed to satisfy the requirements of both expert and average users.
Ease and versatility are significant advantages of Jelastic. End user doesn't have to be a professional to use our product. But at the same time, Jelastic provides great opportunities for those people who use it.
If I needed a platform for SaaS application targeted at Enterprise, I would definitely choose Jelastic.
I cannot directly answer your question (since Layershift are a Jelastic hosting provider), but I can give you more background information that may help with your decision:
Jelastic is provided via a number of different hosting providers right around the world. That means you can combine the ease of use functionality that you mentioned, and use it together with the hosting provider that suits your needs best in terms of physical location, infrastructure details, support, SLAs etc.
Jelastic is also available in a "private cloud" model which allows you to use it either as a self-hosted on-premise solution, or remotely hosted at any datacentre (for example, any existing Jelastic hosting provider can offer this to you easily).
So there's a wide choice of possible solutions available to help you find the best option for your particular needs.
In contrast, IaaS options offered by AWS, Azure, Google etc. give you a single provider. You might like their platform but not their SLA options/prices etc., or you might like their SLA but not their platform - there is no diversity in their offerings.
My answer is NO.
For enterprise product not only we need to consider product itself we also need to take support quality into consideration.
I have been using Jelastic for almost two years and the biggest issues is support quality, the thing is Jelastic Hosting Partners are not trained with Jelastic knowledge, and the support team from Jelastic Hosting Partners can only act as middle man for Jelastic so the real support comes from Jelastic itself, the turnover time is too long for enterprise.
As time of writing, I already waited for my issue for 6 days, and still no response, come on, this is affecting my production!
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
Currently I'm using Azure Logic apps to sync the changes to different 3rd parties.
But it's too expensive when there are massive requests/messages.
The key features:
MQ connector, which can be used as trigger.
HTTP processor, used to issue HTTP requests.
Parse json response.
Possibility to check the history.
I've done some research of Apache Nifi.
My feeling is it's not very user friendly and quite old school.
One close open source option that I know of is n8n.
But you could also explore the fixed pricing model (Integration Service Environment) that logic apps offer, which is charged by the hour instead of based on the volume coming. Depending on the volume fluctuations, you can scale up more units as required.
Also, a completely new (in preview currently) way to develop and run logic app workflows was announced, which introduces a new pricing model (same as app service or premium plan of functions).
This is introduces a docker-based deployment which allows running your logic apps anywhere too.
Apache NiFi can be used for your requirements.
Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data.
It has:
ConsumeMQTT processor which subscribes to a topic and receives messages from an MQTT broker.
InvokeHTTP processor which can interact with a configurable HTTP Endpoint.
Numerous json processors.
Data Provenance feature which tracks dataflow from beginning to end.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm comparing the cost of services like google cloud SQL to launching your own VM in the cloud with whatever sql version you'd like.
VM instance only vs Cloud SQL only
I'm quite surprised by the results I got. The cloud SQL, is more than twice the price for the same underlying system (8 vCPU, 52 Go RAM, 2 To storage)
So basically, you pay more to have less. And I was expecting the contrary...
Granted, you don't have to deal with maintenance and automating backup yourself, but I found the price difference ridicule.
So my question is : when should I consider using Cloud SQL instead of running my own specialized VM ?
Right now, I feel like this service is just a fancy way to milk money from the client.
Note : I took the google Cloud example, but this is the same result with other cloud providers.
The tl;dr answer here is that a VM is very different than a fully-managed service. It's like comparing apples and oranges, honestly.
When you create a VM, you have a VM. You can do whatever you want with it, but it's just a VM. That VM may be subject to restarts, must be totally configured by you in many cases, is not redundant, has no (added) security layer, etc.
As a managed service, Cloud SQL (and other managed services) offer many things way beyond what you can do on just a VM. You mention a fraction of them, such as backups. With a managed service you're getting a ton of other things which really matter to most people, such as:
Updates, upgrades
Better performance (in your example the IOPS of PD and Cloud SQL do not match)
Support for the service
Added security
An IAM layer
Integrations with other services
No need to "build it yourself"
etc...
While a (very) small minority of people may want to roll their own, it's generally a waste of time and a heck of a lot riskier than using a managed service. I think if you asked most any business customer, the cost of a managed service pales in comparison to paying a fleet of people to replicate the benefits you get from one.
This is true for GCP, AWS, and Azure.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I've just taken on a client who needs a subscription based ecommerce site created using ProductCart software. I'm pretty handy with PHP so I should be able to figure out the software. My question is - what are some things i should be aware of when creating a subscription based ecommerce site? What types of questions should I be asking the client? I need to get more specifics from them regarding the different subscription levels and periods, but what other specifics should I get nailed down? I appreciate any help anyone can give.
thanks...
I would highly, highly, HIGHLY (can I make it any more clear) recommend reading and understanding almost everything on this question: What should a developer know before building a public web site?
It outlines all the big things you need to know about Security and Performance for Public Websites, a lot of which apply to e commerce sites. (When people's money is involved, it needs to work right).
Furthermore, you should make sure any certificates you should have are there, encryption, etc.
For Client's Specific Needs:
Signing Up:
Do they want to have promo codes to discount stuff?
Is there a trial period?
Billing:
When does billing occur? (Probably should be doled out throughout the month)
Should there be an interface to change the billing date?
Leaving:
How long does Customer Information stick around?
How much access does a person have to the site when they unsubscribe
Is there a day of grace period (Useful for file-storage sites)
Some of this stuff might be dictated by the package you are using, but still good to have figured out.
smashing magazine has a nice article on things to look for when designing an e-commerce site.
Be sure to ask what types of payment they want to accept. Credit cards? Which ones? E-checks? Paypal? Google checkout? Are card numbers being stored on the payment gateway? If not are you PCI compliant? Do you already have SSL? If not, who's getting the SSL cert? How do you want to handle refunds? Are cancellations pro-rated? Do you want to support affiliates? Do you want to have discount codes? Do subscriptions have setup fees?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I work for a insurance company. We have our own development department made-up of almost 150 people plus some providers (outsourcing and custom made apps pretty much). In our company my team have made what we call non-functional logic libraries. That is, software libraries to handle things that are horizontal to all the development teams in our department, e.g. Security, Webservices, Logging, Messaging and so on. Most or these tools are either made from scratch or adaptation of a de-facto standard. For example our logger is an appender based on Log4J that also saves the logging messages into a DB. We also define what libraries to use in the application, for example which framework for webservices to use. We use pretty much JavaEE and Oracle AS in all our organization (with some Websphere Application servers).
Much of these projects have their architecture documented (use cases, UML diagrams, etc) and generally the generated documentation are available.
Now what we have seen is that for users sometimes is difficult to use the the libraries we provide and the are constantly asking question or they simply don't use them.
So we are planning to generate a more friendly documentation for them, so my question is:
What are the best practices or the checklist that software documentation should have?
Something comes to my mind:
API Reference guide
Quick start Tutorial
API Generated Documentation.
Must be searchable
Web Access
What else should it have? Also, based in your experience what is the best way to maintain (keep it up-to-date) and publish this type of documentation?
Keep your documentation in version control too.
Make sure on every page it has a version number so you know where your user has been reading from.
Get a CI server going and push documentation to a LIVE documentation site upon updates.
Do documentation reviews like you would code reviews.
Dog-food it :)
Kindness,
Dan
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
I need to read the user's fingerprint from my application.
What I really want is a simple SDK that works with a lot of inexpensive fingerprint readers but I can deal with something that works only with one specific model if that model is cheap and available worldwide.
And it has to be royalty-free, I can pay for a development license but if I have to pay for each installation I just can't use it.
What I'm doing has no relation to login or encryption, so the software included with the reader will probably be useless to me.
There is no standard API for reading fingerprint data as far as I'm aware since it is a fairly new field and there's no standard way of doing it. Each manufacturer will provide their own API for reading the hardware. The API could just be IO specification to the hardware and there's no library whatsoever, which makes things a bit trickier. This is down to two factors. The first is that finger print readers are used in many applications - custom hardware, embedded systems through to PC authentication and beyond. Providing software for all those different systems would not be viable from the manufacturers point of view. Secondly, each manufacturer uses a different approach to reading and processing the captured images which would make a common API problematic.
It's an old question, but I bumped into it while researching the topic.
I did find a free library for Linux - libfprint
Digitalpersona has a free SDKs both for windows and linux.
http://www.digitalpersona.com/products/developer.php
I dont know if there are costs for deploying with their SDKs.
(Actually it appears they don't charge per machine/user licensing.)
Did you take a look at the BioAPI consortium site? There's a library for linux over at Google code.
There's also libchipcard, but it doesn't mention fingerprint readers, only smart cards.
Hope that helps.
Symbol has an api for their MC75 handheld devices:
http://support.symbol.com/support/search.do?cmd=displayKC&docType=kc&externalId=12364&sliceId=&dialogID=104336066&stateId=1%200%20104330426
Of course, it only works for their Windows Mobile 6 MC75 devices.
See Windows Biometric Framework.