We design, build and operate cloud-based enterprise data warehouse solutions
Cloud based business intelligence solutions have significant advantages over traditional approaches. We have extensive experience in delivering cost effective and high performance solutions on a massive scale (>100TB) on the AWS platform, in particular using Redshift and EMR (Spark). We specialize in enabling our clients to get value out of cloud based business intelligence solutions and can help with all aspects of this including evaluation, planning, design, development, test, implementation, training and operating.
You may find the following useful if you need to make use of services developed by other teams in the same organisation or you need to make use of third party services, and you want to be more secure and go faster, without having long term architectural disadvantages.
You may find the following useful if you need to analyse how the user experience of the data warehouse varies over the course of recurring time periods such as the working week or financial reporting periods.
You may find the following useful if you need to benchmark the volume of queries on a data warehouse.
You may find the following useful if you need to benchmark the user experience of running queries on a data warehouse.
You may find the following useful if you want to structure the analysis of performance of your data warehouse in order to support tuning as part of improvements work on the same platform, migration to a new platform using the same technology or migration to a new platform on different technology.
You may find the following useful if you need to set up some checks for completeness of processing.
You may find the following useful if you can’t easily see which user stories relate to which functionality, so you can’t tell what the impact on delivery is of a problem with a user story, or you can’t easily get a view on when functionality is expected to be ready because you’re not sure what all the relevant user stories are.
You may find the following useful if you are getting distracted from useful work by efforts to confirm the detail of where your team and others have got up to.
You may find the following useful if you are developing a microservices based solution, and you have direct responsibility for multiple microservices. You want to avoid tight coupling between the microservices you’re directly responsible for, but you want to take advantage of easy communication between teams.
You may find the following useful if you are an architect in an agile team defining your role, or if it is unclear if what the team delivers conforms to the organisation’s architectural principles, or if you are being slowed down by an overload of communication relating to official approvals for delivery.