Need easy cloud based SQL service for non-SQL user.

Hello, I can help out with advice on the technical aspects. Not sure what low-mid budget means for you, but I can tell right off the bat that something like SAP or Salesforce will be overkill. At the base of your tech stack will be the eCommerce platform - i.e. the website - and your back-office - OMS/fulfilment app. For the former, I would opt for a lead developer that can choose the platforms and make sure they can work together. I think getting a small team of 2-3 devs to work closely with merch/sales and content/marketing would save you money and lay a solid groundwork. I can recommend Magento as a solid platform. There's plenty of features to use it standalone, and there are a lot of very good small agencies and a few solid hosting providers. You can even get away with using the free Magento if you get a good team behind it. Need more details from you to get a better understanding of your needs but that should be a good start.

There are a few options. If you've done the basics through Codecademy, then you're ready to move on to the specifics of a platform (such as PostgreSQL as you've mentioned). Though this can equally be a minefield. The reporting engines/formats differ from platform to platform. As does SQL believe it or not, in the sense each of the mainstream vendors adds their own specific bits to the standard. They are all compliant for the basics though. All of them will support the latest version of SQL (ANSI standard 2011), but PL/SQL is different to Transact-SQL in the way it uses cursors. In addition, each has an even bigger variation when it comes to multidimensional queries such as MDX, since there is no standard for MDX and some vendors use their own expressions and languages to carry out such queries. I can certainly help with tutoring, having been working in SQL since 1997 (and still do), although I think it's worth focussing on getting a little better at the specifics of the SQL vendor extensions you want to use, including their Cube, Pivot and Grouping functions as well as more complex joins, as they'll be the baseline skills for future reporting exercises, including analytical processing.

There's 2 types of customers for this segment that have a decent budget. 1) Funded tech startups (i.e. Anyone that recently closed a round on www.angel.co) 2) Digital agencies (or their clients) who want to build a mobile app for marketing or convenience purposes. So for #1, you can target anyone who likes sites like Angel List, Gust, etc. For #2, you can get a list of digital media agencies and run ads against them. All that being said, the best way to pull them into your funnel is to create some AMAZING free content like an infographic, video or webinar that demonstrates why you guys are the best company out there. So teach them something about mobile marketing that they had no clue about - then close them at the end. Hope that helps.

Likely this is the wrong question, so my response is just a guess... from doing software development since 1982... Best to tool your infrastructure, so no load balancers are required. If you design your code where your most accessed data remains memory resident + moving data from persistent storage (disk) into memory is fast, you'll have no requirement for load balancing. You give no information about the size of payload (in bytes) which will be requested, so no way to guess sizing of your net connection. Also you say 1 million status calls + give no time frame over which these calls must be processed. Based on your question, likely your best starting point will be to hire a seasoned developer to design your system to maximize memory resident data. Also, using webhooks may be a poor choice, as this makes code extremely complex, so only a few developers will be able to maintain + extend your code, so you'll pay more for development + have difficulty finding developers. Stick with a LAMP stack allowing Apache to manage threads, rather than Webhooks + your life will be easier + your budget lower.

In Google Cloud, a comprehensive approach to data backup and disaster recovery involves leveraging various services and best practices: 1. Data Backup: Utilize Google Cloud Storage (GCS) for storing backups of your critical data. - Implement automated backup solutions using tools like Cloud Storage Transfer Service or third-party solutions. - Consider snapshotting your virtual machine disks for point-in-time backups. - Implement versioning and lifecycle policies to manage data retention and archival. 2. Disaster Recovery: -Utilize Google Cloud's multi-region and regional redundancy features to ensure high availability and durability of data. - Implement cross-region replication for critical data to ensure redundancy and failover capabilities. - Utilize Google Cloud's managed services like Cloud SQL for database replication and failover. - Design and implement application failover strategies using Google Cloud's load balancing and global routing capabilities. 3. Backup and Recovery Testing: - Regularly test backup and recovery processes to ensure they are effective and meet your recovery time objectives (RTO) and recovery point objectives (RPO). - Conduct disaster recovery drills to simulate real-world scenarios and validate the effectiveness of your disaster recovery plan. - Monitor and audit backup and recovery processes to identify and address any issues or gaps in your disaster recovery strategy. By following these best practices and leveraging Google Cloud's services, you can build a robust data backup and disaster recovery strategy to protect your critical data and ensure business continuity.